directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DIRSERVER-1412) Modifying the schema with more than one mod may fail
Date Tue, 07 May 2013 21:43:16 GMT

     [ https://issues.apache.org/jira/browse/DIRSERVER-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Emmanuel Lecharny resolved DIRSERVER-1412.
------------------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 2.1.0)
                   2.0.0-RC1

The schema modifications are now forbidden.
                
> Modifying the schema with more than one mod may fail
> ----------------------------------------------------
>
>                 Key: DIRSERVER-1412
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1412
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.5.5
>            Reporter: Emmanuel Lecharny
>            Priority: Minor
>             Fix For: 2.0.0-RC1
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message