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 2016/11/14 16:56:59 UTC
[jira] [Updated] (OAK-5105) withIncludeAncestorsRemove should
support **
[ https://issues.apache.org/jira/browse/OAK-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Egli updated OAK-5105:
-----------------------------
Fix Version/s: 1.6
> withIncludeAncestorsRemove should support **
> --------------------------------------------
>
> Key: OAK-5105
> URL: https://issues.apache.org/jira/browse/OAK-5105
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jcr
> Affects Versions: 1.5.13
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Fix For: 1.6, 1.5.14
>
>
> At the moment withIncludeAncestorsRemove is defined to only add {{!deep}} filters for all known parents. However, if you use \*\* you can't know all parents beforehand. So for those glob paths, besides the known parents, we should add the actual, full glob path (for NODE_REMOVED only that is) to the condition (using the trick to not add {{deleteSubtree}} which otherwise filters out subtree deletion).
> As a result you get different events based on the glob path:
> * for all known parents you get an event if one of those parents get removed
> * if you have a glob path registered, then you get an event for all matching paths should a parent of those nodes get deleted
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)