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 2017/07/25 07:51:00 UTC

[jira] [Resolved] (OAK-6487) IndexUpdate should not reindex newly imported index definitions

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

Chetan Mehrotra resolved OAK-6487.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.5

Done with 1802891

> IndexUpdate should not reindex newly imported index definitions
> ---------------------------------------------------------------
>
>                 Key: OAK-6487
>                 URL: https://issues.apache.org/jira/browse/OAK-6487
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: indexing
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: 1.8, 1.7.5
>
>
> IndexUpdate currently decides to reindex any index which is not found in before state i.e. state corresponding to the last checkpointed state. This was done to support cases like OAK-1874 where a new index may not have reindex flag set to true.
> For importing new indexed definitions i.e. where indexing is already done out-of-band by oak-run this poses problem as this new index definition would not be present in before state.
> To account for that this logic should be changed to check if the new index definition is already indexed or not. This can be checked by checking for presence of any hidden node under index definitions. If present then it means that index is already indexed so no need to reindex



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)