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 "Jukka Zitting (JIRA)" <ji...@apache.org> on 2014/03/19 19:59:44 UTC

[jira] [Resolved] (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:all-tabpanel ]

Jukka Zitting resolved OAK-850.
-------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.20)
                   0.19

Done in http://svn.apache.org/r1579349.

When reading, the child order list is automatically synced with the actual set of child nodes by removing all names that are no longer present and adding (to the end of the list in undefined order) all new names that are not yet ordered.

When writing (i.e. adding, removing or ordering child nodes), the child order list is updated to match the above order to prevent the list from diverging further over time.

> 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
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 0.19
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)