jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (Jira)" <j...@apache.org>
Subject [jira] [Commented] (OAK-8579) Composite Node Store: Allow creating an index in the read-only repo first
Date Tue, 27 Aug 2019 12:41:00 GMT

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

Thomas Mueller commented on OAK-8579:

[~tihom88] [~nitigup] [~catholicon] could you review the patch above? 

For the change in NameValidator and TypeEditor: [~stillalex] and [~rombert] you might be a
good reviewer, as the latest changes in those areas were from you.

> Composite Node Store: Allow creating an index in the read-only repo first
> -------------------------------------------------------------------------
>                 Key: OAK-8579
>                 URL: https://issues.apache.org/jira/browse/OAK-8579
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: composite, core, indexing, lucene
>            Reporter: Thomas Mueller
>            Priority: Major
> Currently, it is not allowed to first create a new index in the read-only repository,
and then in the read-write repository. Trying to do so will fail with "OakConstraint0001:
/oak:index/.../:oak:mount-readOnlyV1-index-data[[]]: The primary type null does not exist"
> See OAK-7917: oak-lucene/src/test/java/org/apache/jackrabbit/oak/composite - CompositeNodeStoreLuceneIndexTest.java
tryAddIndexInReadWriteWithIndexExistinginReadOnly line 112. 
> It would be better to allow this use case, to reduce the possibility of problems.
> We should specially test with lucene indexes, but also with property indexes. (If that's
more complicated, we can concentrate on the lucene case first.)

This message was sent by Atlassian Jira

View raw message