[
https://issues.apache.org/jira/browse/OAK-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917381#comment-16917381
]
Nitin Gupta commented on OAK-8579:
----------------------------------
[~tmueller] - One concern that I have here is we might be inadvertently
ignoring/skipping some needed check here .
"The primary type null does not exist" ->Maybe with some test case (trying to
create a node with the higher level jcr api without specifying the primary type
(forcing it to use default)) , we can reproduce this and see why this check is
only coming into picture when index is getting created in read only part of the
repo
> 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
(v8.3.2#803003)
