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/13 16:26:41 UTC
[jira] [Resolved] (OAK-5619) withIncludeAncestorsRemove reports
unrelated top-level node deletion
[ https://issues.apache.org/jira/browse/OAK-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Egli resolved OAK-5619.
------------------------------
Resolution: Fixed
> withIncludeAncestorsRemove reports unrelated top-level node 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
> Fix For: 1.7.0, 1.8, 1.6.1
>
> Attachments: OAK-5619.patch, OAK-5619.patch2
>
>
> 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)