[
https://issues.apache.org/jira/browse/OAK-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354396#comment-14354396
]
Chetan Mehrotra commented on OAK-2598:
--------------------------------------
One possible option can be to move the check for async in
{{IndexUpdate#collectIndexEditors}} to an overridable method. Then in
{{RepositoryUpgrade#createIndexEditorProvider}} we can override the default
[~alex.parvulescu] Thoughts?
> Provide option to run async index as sync in repository upgrade
> ---------------------------------------------------------------
>
> Key: OAK-2598
> URL: https://issues.apache.org/jira/browse/OAK-2598
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: upgrade
> Reporter: Chetan Mehrotra
> Fix For: 1.1.8, 1.0.13
>
>
> Currently when performing repository upgrade from JR2 to Oak the migration
> logic only runs the synchronous index editors. Async indexes like Lucene/Solr
> are run post migration after the system start.
> Given that migration is a single threaded operation it would at times be
> helpful to allow executing such async indexes in sync mode during migration
> phase. This would avoid rescanning of complete repository again for such
> async indexes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
