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

Tomek Rękawek updated OAK-5494:
-------------------------------
    Description: 
Let's assume we have a working instance with multiplexing in place, the /libs 
is mounted in the read-only mode. Now, when an index is created or modified, 
the whole repository (including /libs) will be reindexed. Then, the IndexUpdate 
will try to store part of the generated data to 
{{/oak:index/lucene/:oak:mount-libs-index-data}}. The MultiplexingNodeStore 
won't allow this (as the libs store is a read-only one) - so the whole 
reindexing operation will fail and be started again.

A solution proposal: let's allow to disable mounting the path fragments. 
Indexing data for the libs mount will be stored on the main repository, but 
under a separate path.

> Allow to disable mounting path fragments in the MultiplexingNodeStore
> ---------------------------------------------------------------------
>
>                 Key: OAK-5494
>                 URL: https://issues.apache.org/jira/browse/OAK-5494
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Tomek Rękawek
>            Assignee: Tomek Rękawek
>              Labels: multiplexing
>             Fix For: 1.7.0
>
>
> Let's assume we have a working instance with multiplexing in place, the /libs 
> is mounted in the read-only mode. Now, when an index is created or modified, 
> the whole repository (including /libs) will be reindexed. Then, the 
> IndexUpdate will try to store part of the generated data to 
> {{/oak:index/lucene/:oak:mount-libs-index-data}}. The MultiplexingNodeStore 
> won't allow this (as the libs store is a read-only one) - so the whole 
> reindexing operation will fail and be started again.
> A solution proposal: let's allow to disable mounting the path fragments. 
> Indexing data for the libs mount will be stored on the main repository, but 
> under a separate path.



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

Reply via email to