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 2012/12/19 17:47:13 UTC

[jira] [Resolved] (OAK-531) NodeBuilder deleted child nodes can come back

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

Michael Dürig resolved OAK-531.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.6

Fixed at revision 1423930. Thanks for finding this!
                
> NodeBuilder deleted child nodes can come back
> ---------------------------------------------
>
>                 Key: OAK-531
>                 URL: https://issues.apache.org/jira/browse/OAK-531
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: Alex Parvulescu
>            Assignee: Michael Dürig
>             Fix For: 0.6
>
>         Attachments: OAK-531.patch
>
>
> While working on OAK-520, I've noticed a problem with the NodeBuilder: when we delete an entire hierarchy of nodes and then recreate a part of it, some of the previously deleted nodes can come back.
> This only happens when there are more than 3 levels of nodes.
> So given a hierarchy of nodes: /x/y/z deleted 'x' and simply use the NodeBuilder to traverse down on the same path: .child('x').child('y').
> At this point the 'z' child reappears even though it was deleted before.
> I'll attach a test case shortly.

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