jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (OAK-9290) Respect nt:frozenNode definition on upgrade and migration
Date Tue, 05 Jan 2021 07:50:00 GMT

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

Marcel Reutegger resolved OAK-9290.
    Fix Version/s: 1.38.0
       Resolution: Fixed

Committed PR changes to trunk: http://svn.apache.org/r1885133

Thanks [~stefanegli] for the review.

> 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
> 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

View raw message