[
https://issues.apache.org/jira/browse/OAK-11018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873463#comment-17873463
]
Julian Reschke commented on OAK-11018:
--------------------------------------
There are two questions, I believe:
1. Is it really evil, and should we discourage it (maybe because it would not
work with Jackrabbit classic)?
2. If yes, do things change if, after setting jcr:uuid, the mixin
mix:referenceable is added (back), without an intermediate save operation?
> doc: clarify warning about setting jcr:uuid on non-referenceable nodes
> ----------------------------------------------------------------------
>
> Key: OAK-11018
> URL: https://issues.apache.org/jira/browse/OAK-11018
> Project: Jackrabbit Oak
> Issue Type: Documentation
> Components: doc
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
>
> [https://jackrabbit.apache.org/oak/docs/differences.html#Identifiers] says
> (as per change in OAK-2164):
> {quote}Manually adding a property with the name jcr:uuid to a non
> referenceable node might have unexpected effects as Oak maintains an unique
> index on jcr:uuid properties. As the namespace jcr is reserved, doing so is
> strongly discouraged.
> {quote}
> But the tests for OAK-11000 show that this just works as "expected in Oak"
> (throwing an exception even though no mix:referenceable is present) - as the
> UUID index is maintained even for nodes that do not have mix:referenceable.
> Should we remove or rephrase that warning?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
