jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-2929) Parent of unseen children must not be removable
Date Tue, 08 Sep 2015 14:08:46 GMT

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

Marcel Reutegger commented on OAK-2929:
---------------------------------------

It turns out this is not just a problem for hidden nodes when OAK-2673 feature is enable.
A DocumentNodeStore may apply a conflicting change on visible nodes even when OAK-2673 is
disabled, which is the default.

> Parent of unseen children must not be removable
> -----------------------------------------------
>
>                 Key: OAK-2929
>                 URL: https://issues.apache.org/jira/browse/OAK-2929
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core, mongomk
>    Affects Versions: 1.0.13, 1.2
>            Reporter: Vikas Saurabh
>            Assignee: Marcel Reutegger
>            Priority: Minor
>              Labels: concurrency, technical_debt
>             Fix For: 1.3.6
>
>         Attachments: IgnoredTestCase.patch
>
>
> With OAK-2673, it's now possible to have hidden intermediate nodes created concurrently.
> So, a scenario like:
> {noformat}
> start -> /:hidden
> N1 creates /:hiddent/parent/node1
> N2 creates /:hidden/parent/node2
> {noformat}
> is allowed.
> But, if N2's creation of {{parent}} got persisted later than that on N1, then N2 is currently
able to delete {{parent}} even though there's {{node1}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message