[OAK-5096] node type aggregate filter should be added in OR mode (not in AND)

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.5.13
• Fix Version/s: 1.5.14, 1.6.0
• Component/s: jcr
• Assignee: Stefan Egli
• Reporter: Stefan Egli
• Created: 11/Nov/16 08:14
• Updated: 06/Dec/16 10:37
• Resolved: 14/Nov/16 16:56

Description

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.

Issue Links

• is blocked by: OAK-5099 mixing starstar with star.foo in glob path is broken