[
https://issues.apache.org/jira/browse/OAK-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205035#comment-16205035
]
Vikas Saurabh commented on OAK-6820:
------------------------------------
bq. But then we would need to have different index definitions for upgrade and
non upgrade case.
Ack. Missed this point. Agreed that warn can lead to more confusion.
bq. IndexUpdate would set a hidden flag :disableIndexesOnNextCycle if it finds
during reindexing
Yes, this seems better as we would explicitly be tracking the flow.
> Implement support for disabling indexes which are replaced with newer index
> ---------------------------------------------------------------------------
>
> Key: OAK-6820
> URL: https://issues.apache.org/jira/browse/OAK-6820
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: indexing
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: 1.8
>
> Attachments: OAK-6820-v1.patch
>
>
> For upgrade case in many applications older index type is set to {{disabled}}
> when new index is provisioned. If the new index is async then it would take
> some time for reindex and till then any query which used to make use of old
> index would end up traversing the repository
> To avoid such a scenario we should only mark older index as "disabled" only
> if the newer index is reindex.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
