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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2016/05/03 15:44:13 UTC

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

     [ https://issues.apache.org/jira/browse/OAK-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra updated OAK-3981:
---------------------------------
    Labels:   (was: docs-impacting)

> 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
>             Fix For: 1.4, 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)