https://bugzilla.redhat.com/show_bug.cgi?id=739172
When using fractional replication, there is a single list of attributes to exclude that is used for both total update and incremental updated replication protocols. While this is generally what one wants to do, it would be nice to have the ability to have separate attribute lists for each protocol. In the case where you are using a plug-in like memberOf, you want to exclude the memberOf attribute from replication to allow each replica to generate it's own memberOf attributes. This makes sense for the incremental update protocol, but there is no reason to exclude it from total update, as the memberOf consistency is in a known good state. If we could replicate memberOf for total update, there would be no need to run a potentially costly memberOf fixup task on each replica after it is initialized.
commit changeset:0157534/389-ds-base Author: Nathan Kinder nkinder@redhat.com Date: Fri Sep 16 10:01:08 2011 -0700 This patch adds the ability to have a separate fractional attribute list for the incremental and total update replication protocols.
A new nsDS5ReplicatedAttributeListTotal attribute can be added to a replication agreement to list the attributes to exclude from the total update protocol. This has the same format as the existing nsDS5ReplicatedAttributeList attribute. If a separate total update attribute list is not specified, the nsDS5ReplicatedAttributeList value will be used for both incremental and total update. To use a total update attribute list, an incremental list must be specified as well.
Added initial screened field value.
Metadata Update from @nkinder: - Issue assigned to rmeggins - Issue set to the milestone: 1.2.10
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/250
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.