You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2007/04/03 06:33:32 UTC
[jira] Created: (DIRSERVER-893) All schema changes lost after
restart
All schema changes lost after restart
-------------------------------------
Key: DIRSERVER-893
URL: https://issues.apache.org/jira/browse/DIRSERVER-893
Project: Directory ApacheDS
Issue Type: Bug
Components: schema
Environment: Any
Reporter: Alex Karasulu
Assigned To: Alex Karasulu
Priority: Blocker
Fix For: 1.5.0
All schema changes made to the schema partition via direct alterations under ou=schema or to changes made on the schemaSubentry are seem not to persist. I researched this problem and it appears as though it is due to the initialization code not checking to make sure the schema partition is already present. As it stands the schema files are being overwritten on restarts.
This problem was just discovered and fixed. Commits will follow soon.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRSERVER-893) All schema changes lost after
restart
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu closed DIRSERVER-893.
-----------------------------------
Resolution: Fixed
This was fixed in the pre-release branch and in the trunk with the following commits:
https://svn.apache.org/viewvc?view=rev&revision=525035
https://svn.apache.org/viewvc?view=rev&revision=525039
> All schema changes lost after restart
> -------------------------------------
>
> Key: DIRSERVER-893
> URL: https://issues.apache.org/jira/browse/DIRSERVER-893
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: schema
> Environment: Any
> Reporter: Alex Karasulu
> Assigned To: Alex Karasulu
> Priority: Blocker
> Fix For: 1.5.0
>
>
> All schema changes made to the schema partition via direct alterations under ou=schema or to changes made on the schemaSubentry are seem not to persist. I researched this problem and it appears as though it is due to the initialization code not checking to make sure the schema partition is already present. As it stands the schema files are being overwritten on restarts.
> This problem was just discovered and fixed. Commits will follow soon.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.