[
https://issues.apache.org/jira/browse/OAK-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107115#comment-16107115
]
Tomek Rękawek commented on OAK-4891:
------------------------------------
[~rombert] - sure. I'd say that the runtime checks are covered:
* the CrossMountReferenceValidator takes care of the cross-mount references
OAK-6256,
* ReferenceEditorProvider won't allow to create a reference with missing target,
* PropertyIndexEditorProvider doesn't allow to create duplicate entries on two
different mounts.
With regards to the mount-time checks, I think we can't forbid the
referenceable nodes completely, as the {{nt:file}} is referenceable. That's why
the OAK-6256 looks for cross-mount references, not for any referenceable nodes.
I think it'd be good to use the same logic in the mount time as well (as in my
comment to OAK-6445 - it'll work even without a commit).
+1 to the uniqueness. I don't have any other mount-time tests in mind right now.
> Mount-time sanity checks for mounted NodeStore instances
> --------------------------------------------------------
>
> Key: OAK-4891
> URL: https://issues.apache.org/jira/browse/OAK-4891
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: core
> Reporter: Robert Munteanu
> Assignee: Tomek Rękawek
> Fix For: 1.8, 1.7.6
>
>
> When mounting a NodeStore we should be able to run a quick sanity check to
> make sure that it does not use any features which are troublesome, notably
> those which would contribute to one of the 'global' states of Oak:
> - versioned nodes
> - referenceable nodes
> - etc ( more TDB )
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
