directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DIRSERVER-849) Lacking atomicity for modify operations on schema subentry
Date Sat, 18 Aug 2007 02:58:30 GMT

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

Alex Karasulu updated DIRSERVER-849:
------------------------------------

    Affects Version/s: 1.5.1
        Fix Version/s:     (was: 1.5.1)
                       1.5.2
              Summary: Lacking atomicity for modify operations on schema subentry  (was: Subentry
modfications are not atomic)

Ersin you're intuition is right - I was in fact referring specifically to the schema subentries.
 I have edited the subject of the issue and delayed this for 1.5.2.

> 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: 1.5.2
>
>
> 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