You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/03/19 10:02:38 UTC

[jira] [Resolved] (OAK-2598) Provide option to run async index as sync in repository upgrade

     [ https://issues.apache.org/jira/browse/OAK-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra resolved OAK-2598.
----------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: 1.0.13)
                       (was: 1.1.8)
         Assignee: Chetan Mehrotra

Thinking about it further such a feature would not be usable for the primary usecase of migration. As JR2 used to depend on Lucene 3.x while Oak depends on Lucene 4.x its not possible to easily use LuceneIndexProvider while migration.  So closing for now

> 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
>            Assignee: Chetan Mehrotra
>
> 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)