[
https://issues.apache.org/jira/browse/OAK-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203153#comment-16203153
]
Vikas Saurabh commented on OAK-6820:
------------------------------------
Other than what we discussed the other about that IndexUpdate would now need
some sort of understanding of index def, the idea seems fine to me.
Btw, this opens up another question: while sure disabling a prop index is the
quickest way - but, maybe, we should also need to expose some jmx to clean up
such indices - maybe your recursive delete (OAK-6787) could become useful in
this case too? Yes, that' a separate issue, of course.
> 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
>
>
> 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)
