#48031 Replication of the schema: comparison should also be possible on extension (e.g. X-VERSION)
Closed: wontfix by spichugi. Opened by tbordaz.

Currently a supplier/consumer sends/accepts the schema at the condition that the new schema is a superset of the current one.
For objectclasses attribute this is done based on comparison of required/allowed attributetypes
For attributetypes this is done based on comparison of single/multi valued and syntax.

Comparison could also be based on object extension (like X-VERSION) where a newer version should sent/accepted.


no clone, can be covered by upstream tests

Hi Thierry,

Is this ticket a defect or an enhancement? Is this for making the decision to replicate schema more accurate?

How urgent is this requirement?

Hi Noriko,

This ticket is an enhancement on how to replicate the schema. It would give more flexibility to application to decide which definitions should supersede the others.

This enhancement is asked by freeipa but the support of the enhancement in freeipa is not yet planed.
Currently the first freeipa release that can support this would be 4.4 that should be part of F24.

So there is no urgent requirement for it.

thanks
thierry

Thank you for the clarification, Thierry!

Pushing the milestone to 1.3.5 backlog...

Per triage, push the target milestone to 1.3.6.

Metadata Update from @nhosoi:
- Issue set to the milestone: 1.3.6.0

Metadata Update from @mreynolds:
- Custom field component reset (from Replication - General)
- Custom field rhbz reset (from 0)
- Issue set to the milestone: 1.4 backlog (was: 1.3.6.0)

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Issue tagged with: Schema

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1362

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

Metadata