[DIRSERVER-1412] Modifying the schema with more than one mod may fail

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 1.5.5
• Fix Version/s: 2.0.0-M16
• Assignee: Unassigned
• Reporter: Emmanuel Lécharny
• Created: 26/Sep/09 07:20
• Updated: 19/May/19 10:13
• Resolved: 07/May/13 21:42

Description

When applying some schema modification as one single modify() operation, if there are more than one schema modifications, we may have failures :

• first we can't guarantee the atomicity as all the parsing are done first, and as the integrity check are done during parsing, we have corner case which will throw an exception. For instance, if we have 2 AT being injected, one being the other's superior, as the superior has not been injected into the schema, the second AT may complain about the missing superior AT
• second if for some reason we have a failure in the middle of the processing, we won't be able to revert all the previous additions.

Both issues can be fixed, but I'm not sure it worth the pain of having a shadow registry in which we apply the changes until we are sure we are fine with all the modifications, before updating the real schema.

IMO, that would be better to forbid schema modifications with more than one modification in the modify parameters. A slight violation of the protocol, but really not that important.