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 "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2017/08/23 13:08:00 UTC

[jira] [Commented] (OAK-6577) Determine the approach for reindexing in case of CompositeNodeStore setups

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

Vikas Saurabh commented on OAK-6577:
------------------------------------

Quick thought: maybe we should distinguish between re-index of shared store due to index def change (where index def changes are allowed only as system upgrade/update of private-read-only-mount).

In absence of index def changes (reindex due to corrupt index) should then be doable to only reindex read-write mount.

I mean solving reindex in general without context might be a harder problem v/s breaking into use-cases.

> Determine the approach for reindexing in case of CompositeNodeStore setups
> --------------------------------------------------------------------------
>
>                 Key: OAK-6577
>                 URL: https://issues.apache.org/jira/browse/OAK-6577
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: composite, indexing
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.8
>
>
> Current index tooling is designed to work with a single NodeStore setups. We should determine how reindexing should be done for CompositeNodeStore setup specially where one of the mount is private and read only



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)