[
https://issues.apache.org/jira/browse/OAK-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132206#comment-15132206
]
Chetan Mehrotra edited comment on OAK-3981 at 2/5/16 5:00 AM:
--------------------------------------------------------------
Added a new property definition config {{excludeFromAggregation}} which can be
used to exclude a property from being used in aggregation. Otherwise all
properties of nodes covered by aggregation are included if there type matches
Fixed with
* trunk - 1728443
* 1.0 - 1728445
* 1.2 - 1728447
was (Author: chetanm):
Fixed with
* trunk - 1728443
* 1.0 - 1728445
* 1.2 - 1728447
> Change in aggregation flow in OAK-3831 causes some properties to be left out
> of aggregation
> -------------------------------------------------------------------------------------------
>
> Key: OAK-3981
> URL: https://issues.apache.org/jira/browse/OAK-3981
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
> Affects Versions: 1.3.13, 1.0.26, 1.2.10
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Labels: docs-impacting
> Fix For: 1.2.11, 1.0.27, 1.3.16
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
