You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2010/06/02 20:23:40 UTC

[jira] Resolved: (DIRSERVER-1155) Use the rollback mechanism to restore the base when schema is modified

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

Emmanuel Lecharny resolved DIRSERVER-1155.
------------------------------------------

    Resolution: Fixed

The way we handle the schema right now forbid the injection of a wrong schema. The nexly modified schema is always tested against inconsistancies, and rollbacked if proved to be wrong

> Use the rollback mechanism to restore the base when schema is modified
> ----------------------------------------------------------------------
>
>                 Key: DIRSERVER-1155
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1155
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>            Reporter: Emmanuel Lecharny
>             Fix For: 2.0.0-RC1
>
>
> It would be a great improvement to be able to rollback a schema modification if the schema is invalid. 
> For instance, injecting a wrong schema will result in an error when restarting the server, forbiding you to use the server anymore, unless the schema directory is destroyed.
> This is axceptable if you inject the modifications in one shot, but certainly not if it's done little by little.
> I wouls suggest that we track schema modifications somwhere in the DIT (like what we do with LDIF inject files), and allow the user to launch the server with an option telling the server to restart in the latest correct schema version.
> Another option would be to revert to the previous version if we get an error while loading the schema.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.