You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org> on 2011/08/26 18:24:31 UTC
[jira] [Created] (DIRSERVER-1648) Disabling a schema should throw
an error when there are still entries depending on that schema in the DIT
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.0.0-M3
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSERVER-1648) Disabling a schema should throw
an error when there are still entries depending on that schema in the DIT
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465388#comment-13465388 ]
Emmanuel Lecharny commented on DIRSERVER-1648:
----------------------------------------------
This is extremely problematic. The only simple way to get this fixed would be to check *all* the entries to see if they are using the disabled schema, and it would take a very long time....
> 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.0.0-RC1
>
>
> 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
[jira] [Updated] (DIRSERVER-1648) Disabling a schema should throw
an error when there are still entries depending on that schema in the DIT
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ 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