You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Kiran Ayyagari (JIRA)" <ji...@apache.org> on 2009/08/27 16:40:59 UTC
[jira] Created: (DIRSERVER-1406) Rejecting an incorrect LDIF entry
of config or schema partitions and reverting it to the last known stable
state
Rejecting an incorrect LDIF entry of config or schema partitions and reverting it to the last known stable state
----------------------------------------------------------------------------------------------------------------
Key: DIRSERVER-1406
URL: https://issues.apache.org/jira/browse/DIRSERVER-1406
Project: Directory ApacheDS
Issue Type: New Feature
Components: schema
Reporter: Kiran Ayyagari
Priority: Minor
Fix For: 2.5.0
(excerpt from the IRC chat on #apache-directory-dev)
Basically if we encounter an LDIF that is incorrect or correct yet invalid based on schema information during the LDIF entry validation stage, then the server will ...
1). not accept the alteration made (we have timestamps and a changelog to detect this)
2). move the change to original-file-name.rejected
3). revert the old state of that schema object using the changelog
The combination of options 2&3 will be cool to have so that we can always keep the server in a stable running condition (assuming that it was started initially from a correct base) or can be restarted without having problems if it was started after making a wrong configuration/schema change.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.