[
https://issues.apache.org/jira/browse/OAK-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15445345#comment-15445345
]
Vikas Saurabh commented on OAK-4714:
------------------------------------
bq. Now with hybrid index this can be handled better. For hybrid index - The
index state can still be updated on each cluster node (based on old index
definition) which async indexing is busy in reindexing phase. End query result
would include recent changes and hence would not be stale due to async index
lagging with reindexing work.
I think this might lead to unexpected behaviors when re-indexing is being done
due to index def changes. I think a consistent result set (even if it's older)
is easier to reason with than with mixed results.
Moreover, I feel that re-indexing is a not-so-frequently occurring
administrative task - and stale results during that period might be acceptable.
> Reindexing should only happen in async mode for a mix mode index definition
> ---------------------------------------------------------------------------
>
> Key: OAK-4714
> URL: https://issues.apache.org/jira/browse/OAK-4714
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Affects Versions: 1.5.8
> Reporter: Chetan Mehrotra
> Priority: Minor
> Fix For: 1.6
>
>
> With OAK-4641 support was added for enabling use of same index definition for
> both async and sync mode. This causes issue for reindexing as with this
> change it would be attempted for both modes.
> Instead for a mixed mode index definition reindexing should be bounded to
> only one of the modes and only for that mode reindexing should be performed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
