You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Stefan Egli (Jira)" <ji...@apache.org> on 2021/03/03 13:21:00 UTC
[jira] [Updated] (OAK-9134) Remove mix:referenceable from
nt:frozenNode definition
[ https://issues.apache.org/jira/browse/OAK-9134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Egli updated OAK-9134:
-----------------------------
Fix Version/s: 1.22.7
> Remove mix:referenceable from nt:frozenNode definition
> ------------------------------------------------------
>
> Key: OAK-9134
> URL: https://issues.apache.org/jira/browse/OAK-9134
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, jcr
> Reporter: José Andrés Cordero Benítez
> Assignee: José Andrés Cordero Benítez
> Priority: Minor
> Labels: patch
> Fix For: 1.34.0, 1.22.7
>
> Attachments: OAK-9134-remove-referenceable-from-test.patch, OAK-9134-remove-referenceable-frozenNode-2.patch, OAK-9134-remove-referenceable-frozenNode-3.patch, OAK-9134-remove-referenceable-frozenNode-4.patch, OAK-9134-remove-referenceable-frozenNode.patch, OAK-9134.additional.test.patch
>
>
> 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|https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.13.4.1%20nt:frozenNode].
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)