On 03/06/2019 12:08, Florian Caillet wrote: > Hello, > > To improve performance, I'm working on changes of LSC, dealing with MERGE > policy. > In LSC v2.1, when you're synchronising a multivalue attributes (for example > "member" attribute) with MERGE policy. Only "adds" are synchronised and > generated in LDIF flow. > I'm developping changes to manage deleted values. Are you interested with > this option ? > What is the best way to integrate in LSC project ? Change the MERGE behaviour > or add a new synchronising policy ? >
Hi Florian, I don't think changing the behaviour of the MERGE a good idea, not in a minor version update anyway; MERGE strategy allows managing attributes in the destination while getting new addition from SRC. Its simple and works well for simple multi-valued attributes. Could you clarify what exact rules you would set up to decide whether to delete or ignore an attribute in this new strategy ? What would LSC check to trigger a deletion ? Experience shows that everybody have specific use cases and different expectations on what a merge strategy should do with member attributes. With a usecase that require some sort of merge rules, I would use a FORCE strategy that perform the merge, because mapping member attributes between SRC and DST is always specific, and also the logic behind the merge is easier to understand for maintainers because it is scripted in the configuration. Could you explain your use case, how you currently handle it, and why you think performance is an issue ? Regards, > Let's exchange about that... > > Thanks, > > -- > > *Florian CAILLET* > -- Soisik Froger | Software Architect [email protected] Worteks | https://www.worteks.com _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] https://lists.lsc-project.org/cgi-bin/mailman/listinfo/lsc-users
