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 "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2016/06/03 11:03:59 UTC

[jira] [Commented] (OAK-4420) RepositorySidegrade: oak-segment to oak-segment-tar should migrate checkpoint info

    [ https://issues.apache.org/jira/browse/OAK-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313969#comment-15313969 ] 

Tomek Rękawek commented on OAK-4420:
------------------------------------

[~alex.parvulescu], I've prepared a naive fix, which copies the /checkpoints from the old repository to the new one using the RepositoryCopier, in a similar way as the repository content root is copied. It works, but it'll probably multiply the target repository size, as the root node will be copied for each existing checkpoint.

If I understand correctly, the /checkpoints/.../root node shouldn't contain a full copy of the repository but just a reference to a given revision. I'm not sure how we can achieve this in the oak-upgrade, which works on the node store level and doesn't really know anything about segment or document implementation specifics. Any ideas?

> RepositorySidegrade: oak-segment to oak-segment-tar should migrate checkpoint info
> ----------------------------------------------------------------------------------
>
>                 Key: OAK-4420
>                 URL: https://issues.apache.org/jira/browse/OAK-4420
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segment-tar, upgrade
>            Reporter: Alex Parvulescu
>            Assignee: Tomek Rękawek
>         Attachments: OAK-4420-naive.patch
>
>
> The sidegrade from {{oak-segment}} to {{oak-segment-tar}} should also take care of moving the checkpoint data and meta. This will save a very expensive full-reindex.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)