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 "Ian Boston (JIRA)" <ji...@apache.org> on 2015/10/13 12:22:05 UTC

[jira] [Commented] (OAK-3505) Provide an optionally stricter policy for missing synchronous index editor providers

    [ https://issues.apache.org/jira/browse/OAK-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954762#comment-14954762 ] 

Ian Boston commented on OAK-3505:
---------------------------------

For discussion however brief.

Where a repository already has reindex=true persisted for whatever reason and will not accept commits without first rebuilding all indexes synchronously, it would be helpful to have a recovery mechanism that could be activated OSGi container startup eliminating the need to edit the repository via oak-run, osgi console, native DB access, custom oak-core bundle. Any method can be applied before startup would be enough. Failing that, some other recovery mechanism.

> Provide an optionally stricter policy for missing synchronous index editor providers
> ------------------------------------------------------------------------------------
>
>                 Key: OAK-3505
>                 URL: https://issues.apache.org/jira/browse/OAK-3505
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>
> Currently a missing synchronous index editor provider will mark the specific index type with a reindex flag (OAK-3366). I'd like to provide the option to setup a strategy to fail the commit until a specific impl comes online.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)