[OAK-3981] Change in aggregation flow in OAK-3831 causes some properties to be left out of aggregation

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.26, 1.2.10, 1.3.13
• Fix Version/s: 1.0.27, 1.2.11, 1.3.16, 1.4
• Component/s: lucene
• Assignee: Chetan Mehrotra
• Reporter: Chetan Mehrotra
• Created: 04/Feb/16 08:00
• Updated: 03/May/16 13:43
• Resolved: 04/Feb/16 11:50

Description

With OAK-3831 we change the aggregation logic to avoid indexing those relative properties for which there is a property definition defined but nodeScopeIndex is false.

This causes regression as so far such properties were getting included via the aggregation rules and now they would be left out cause search to miss on those terms.

As a fix we should revert to old logic and provide a new flag for enabling exclusion of property from getting aggregated

Issue Links

• is broken by: OAK-3831 Allow relative property to be indexed but excluded from aggregation