[
https://issues.apache.org/jira/browse/DIRSERVER-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1648:
-----------------------------------------
Component/s: schema
ldap
> Disabling a schema should throw an error when there are still entries
> depending on that schema in the DIT
> ---------------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1648
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1648
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: ldap, schema
> Affects Versions: 2.0.0-M2
> Reporter: Pierre-Arnaud Marcelot
> Priority: Blocker
> Fix For: 2.1.0
>
>
> Following DIRSERVER-1647 (Unable to enable/modify/delete schema), I think
> there's a big issue in the case where we're disabling a schema.
> We should throw an error when there are still entries depending on that
> schema in the DIT.
> Currently it ends successfully, leaving the database in a not coherent state.
> Any restart of the server will fail after this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
