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 2008/03/22 00:15:24 UTC
[jira] Created: (DIRSERVER-1155) Use the rollback mechanism to
restore the base when schema is modified
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
Affects Versions: 1.5.1
Reporter: Emmanuel Lecharny
Priority: Critical
Fix For: 2.0.0
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.
[jira] Commented: (DIRSERVER-1155) Use the rollback mechanism to
restore the base when schema is modified
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581234#action_12581234 ]
Alex Karasulu commented on DIRSERVER-1155:
------------------------------------------
I like the sound of this. I think this should work as is now. Are you sure this does not? To the change log system schema changes are seen as any other change that can be rolledback. We should be using it for schema subsystem tests which are rolled back in the core-unit module. At least this is what I think but I may 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
> Affects Versions: 1.5.1
> Reporter: Emmanuel Lecharny
> Priority: Critical
> Fix For: 2.0.0
>
>
> 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.
[jira] Commented: (DIRSERVER-1155) Use the rollback mechanism to
restore the base when schema is modified
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581256#action_12581256 ]
Emmanuel Lecharny commented on DIRSERVER-1155:
----------------------------------------------
Yes, it should be quite straightforward to implement it. We may even simply choose to revert to the previous configuration, if some problem arise. We just have to tag the correct version.
At lelast, I would say we have all the needed mechanisms to implement this feature, we just have to double think about what would be the best implementation from the user point of view to. I will try to describe some scenario for this.
> 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
> Affects Versions: 1.5.1
> Reporter: Emmanuel Lecharny
> Priority: Critical
> Fix For: 2.0.0
>
>
> 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.
[jira] Updated: (DIRSERVER-1155) Use the rollback mechanism to
restore the base when schema is modified
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1155:
-----------------------------------------
Fix Version/s: 2.0.0-RC1
(was: 2.0.0)
Moved back to 2.0.0-RC1
> 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.
[jira] Updated: (DIRSERVER-1155) Use the rollback mechanism to
restore the base when schema is modified
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-1155:
-------------------------------------
Priority: Major (was: Critical)
Affects Version/s: (was: 1.5.1)
This is not critical IMHO.
> 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
>
>
> 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.
[jira] Resolved: (DIRSERVER-1155) Use the rollback mechanism to
restore the base when schema is modified
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (DIRSERVER-1155) Use the rollback mechanism to
restore the base when schema is modified
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny closed DIRSERVER-1155.
----------------------------------------
> 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.