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.
Created attachment 523589 [details]
*** Bug 739176 has been marked as a duplicate of this bug. ***
If you specify a list of fractional attributes for incremental protocol, and you do not specify a list for total protocol, will total protocol use the list of the incremental attributes?
(In reply to comment #3)
> If you specify a list of fractional attributes for incremental protocol, and
> you do not specify a list for total protocol, will total protocol use the list
> of the incremental attributes?
Yes. I did this to remain backwards compatible. I don't want someone upgrading to suddenly find that attributes they want completely excluded (like passwords) are being pushed to replicas during initialization.
Pushed to master. Thanks to Rich and Noriko for their reviews!
Counting objects: 25, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (13/13), done.
Writing objects: 100% (13/13), 2.19 KiB, done.
Total 13 (delta 11), reused 0 (delta 0)
6120b3d..0157534 master -> master
Marking this bug as Verified since the clone has been verified successfully.