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 2016/11/05 15:14:58 UTC

[jira] [Commented] (OAK-3680) Partial re-index from last known good state

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

Chetan Mehrotra commented on OAK-3680:
--------------------------------------

Interesting idea. We can possibly save the checkpoint as part of index data. So we can see if that has yet not expired then provide a way to trigger indexing for that specific index from that checkpoint

> Partial re-index from last known good state
> -------------------------------------------
>
>                 Key: OAK-3680
>                 URL: https://issues.apache.org/jira/browse/OAK-3680
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: lucene, query
>    Affects Versions: 1.0, 1.2
>            Reporter: Michael Marth
>            Assignee: Chetan Mehrotra
>              Labels: resilience
>
> ATM indexes break (by whatever circumstances) users need to perform a full re-index. Depending on the size off the repository this can take a long time.
> If the user knows that the indexes were in a good state at a certain revision in the past then it would be very useful, if the user could trigger a "partial" re-index where only the content added after a certain revision was updated in the index.



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