directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DIRSERVER-849) Lacking atomicity for modify operations on schema subentry
Date Sun, 30 May 2010 09:49:37 GMT

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

Emmanuel Lecharny resolved DIRSERVER-849.
-----------------------------------------

    Resolution: Fixed

The subschemasubentry management has been completely reviewed last year.

The mentionned problem should not occur anymore, as the way we now handling schema modification
is :
- clone the entire schema
- apply the modifications
- check if the cloned schema is consistent
  - if not, ditch the cloned schema, and keep the previous one, then produce an error message
  - otherwise swap the old schema out and replace it with the new schema.

> Lacking atomicity for modify operations on schema subentry
> ----------------------------------------------------------
>
>                 Key: DIRSERVER-849
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-849
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: schema
>    Affects Versions: 1.5.1, 1.5.0
>            Reporter: Alex Karasulu
>             Fix For: 2.0.0-RC1
>
>
> Sometimes a modify operation may add or remove multiple schema entities.  If one is bad
yet others are not the modification for the bad entity is rejected while others are not. 
This failure of one entity should cause the entire operation to rollback to preserve atomicity
of the modify operation on the schema subentry.

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


Mime
View raw message