You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2013/05/30 10:54:20 UTC

[jira] [Commented] (OAK-850) Degrade gracefully when :childOrder is out of sync

    [ https://issues.apache.org/jira/browse/OAK-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13670167#comment-13670167 ] 

Michael Dürig commented on OAK-850:
-----------------------------------

FTR: an other situation where out of sync. currently happens is when a node is removed an the session does not have access to the parent node due to access control. See also OAK-842.
                
> Degrade gracefully when :childOrder is out of sync
> --------------------------------------------------
>
>                 Key: OAK-850
>                 URL: https://issues.apache.org/jira/browse/OAK-850
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Marcel Reutegger
>            Priority: Minor
>
> One of the possible side effects of OAK-846 (before the fix) was a :childOrder, which is out of sync with the actual child nodes. This usually cannot happen, because both modification to the :childOrder and the child nodes are atomic. Oak should degrade gracefully if it happens anyway and not fail with an unspecified exception.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira