Description
One of the changes between JCR 1.0 and JCR 2.0 is the definition of nt:frozenNode. In JCR 1.0 the node type extends from mix:referenceable, while in JCR 2.0 it does not anymore.
Oak currently uses a nt:frozenNode definition that extends from mix:referenceable. This adds quite a bit of overhead because each node written under a JCR version gets a jcr:uuid, which is indexed by default.
The proposal is to remove the supertype "mix:referenceable" from nt:frozenNode.
Removing this supertype, the frozenNodes wouldn't have a "jcr:uuid" field, which at the end is not used, and allows to reduce the size of the index.
Attachments
Attachments
Issue Links
- relates to
-
OAK-9131 oak-run tool for scanning for references to nt:frozenNode
- Closed
-
JCR-4618 Relax PredefinedNodeTypeTest to not require nt:frozenNode to be referenceable
- Closed
-
OAK-9290 Respect nt:frozenNode definition on upgrade and migration
- Closed
-
OAK-9291 Refactor check for referenceable nt:frozenNode definition
- Closed
- links to