[
https://issues.apache.org/jira/browse/DIRSERVER-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1648:
-----------------------------------------
Fix Version/s: (was: 2.0.0-RC1)
2.1.0
We can fix that the same way we did for the index creation when the index is
created after some data has been injected :
we check all the entries, and if we find one with the deleted element, we can
either remove the entry, or inform the user that the element is in use.
However, it's a huge modification. I suggest we postpone it to a later version
> 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
> 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 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
