[
https://issues.apache.org/jira/browse/OAK-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657374#comment-15657374
]
Stefan Egli commented on OAK-5096:
----------------------------------
Another fix for this : http://svn.apache.org/viewvc?rev=1769310&view=rev
"when switching from AND to OR one must assure that the aggregated subpaths are
also added to the include paths - both to the prefilter and the filter
conditions - earlier in AND mode this was assured via the
NodeTypeAggregationFilter but now this is no longer used"
> node type aggregate filter should be added in OR mode (not in AND)
> ------------------------------------------------------------------
>
> Key: OAK-5096
> URL: https://issues.apache.org/jira/browse/OAK-5096
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Affects Versions: 1.5.13
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Priority: Blocker
> Fix For: 1.5.14
>
>
> [~cziegeler] reported the following: The node type aggregate filter
> introduced in OAK-5021 ({{OakEventFilter.withNodeTypeAggregate}}) currently
> is added in 'AND' mode. That means its conditions must be fulfilled
> additionally to the other filter settings in order for an event to be
> generated. This is somewhat counter intuitive as the expectation is that this
> should be in 'OR' mode, which means all it should do is aggregate changes
> under a certain node type (based on certain sub paths) into a parent path (by
> using the identifier) but it should still send out all other events normally.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
