[
https://issues.apache.org/jira/browse/OAK-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16048696#comment-16048696
]
Chetan Mehrotra commented on OAK-6344:
--------------------------------------
After thinking about it I realized that we need to be careful here. If the new
set of included path is subset of former then only avoid resetting reindex
flag. To start if any index did not had any include exclude set then its ok to
specify a new set of include path
> IndexDefinitionBuilder should not set reindex flag on additional include paths
> ------------------------------------------------------------------------------
>
> Key: OAK-6344
> URL: https://issues.apache.org/jira/browse/OAK-6344
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Minor
> Fix For: 1.8
>
>
> Additional include paths doesn't require indices to be rebuilt to be usable.
> But, currently, provisioning an index with just an additional include path
> would set the reindex flag. While reindexing would indeed clean up some
> indexed paths - but reindexing isn't necessary in this case. Otoh, reindexing
> comes with a heavy cost.
> So, it might be useful to not set reindex flag on additional included paths.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
