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 Marth (JIRA)" <ji...@apache.org> on 2014/03/18 15:09:44 UTC

[jira] [Updated] (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 ]

Michael Marth updated OAK-850:
------------------------------

    Fix Version/s:     (was: 1.0)
                   0.20

> 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
>             Fix For: 0.20
>
>
> 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)