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 17:09:00 UTC

[jira] [Updated] (OAK-9290) Respect nt:frozenNode definition on upgrade and migration

     [ https://issues.apache.org/jira/browse/OAK-9290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Egli updated OAK-9290:
-----------------------------
    Fix Version/s: 1.22.7

> Respect nt:frozenNode definition on upgrade and migration
> ---------------------------------------------------------
>
>                 Key: OAK-9290
>                 URL: https://issues.apache.org/jira/browse/OAK-9290
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, upgrade
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.38.0, 1.22.7
>
>
> With OAK-9134 the nt:frozenNode definition was changed and new repositories created with Oak 1.34 or newer create frozen nodes that are not referenceable anymore.
> The migration component in oak-core (org.apache.jackrabbit.oak.plugins.migration) always copies versions from the source to the target as is. That is, a migration from an old repository to a new one may result in frozen nodes that are not referenceable but still have a jcr:uuid property. The migration should respect the nt:frozenNode definition on the target and omit the jcr:uuid property when the frozen node is not referenceable.
> Similarly, the oak-upgrade component has a side-grade feature that needs adjustment.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)