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 "Stefan Egli (JIRA)" <ji...@apache.org> on 2017/02/09 10:27:41 UTC

[jira] [Commented] (OAK-5619) withIncludeAncestorsRemove reports unrelated parent deletion

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

Stefan Egli commented on OAK-5619:
----------------------------------

Added a test case to trunk (currently disabled) with which this can be reproduced: http://svn.apache.org/viewvc?rev=1782304&view=rev

> withIncludeAncestorsRemove reports unrelated parent deletion
> ------------------------------------------------------------
>
>                 Key: OAK-5619
>                 URL: https://issues.apache.org/jira/browse/OAK-5619
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: jcr
>    Affects Versions: 1.6.0
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>            Priority: Critical
>
> withIncludeAncestorsRemove includes deletion of all parents of the registered paths. When registering an include path {{/a/b/c}} this thus triggers an event if {{/a}} is deleted. When registering an include glob path {{**/foo}} then any parent path deletion will be reported.
> There is a bug currently whereas an include path {{/a/b/c}} results in any parent deletion to be reported. This likely stems from the fact that for glob paths any parent path deletion will be reported.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)