[
https://issues.apache.org/jira/browse/OAK-6531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123974#comment-16123974
]
Michael Dürig commented on OAK-6531:
------------------------------------
At http://svn.apache.org/viewvc?rev=1804851&view=rev I implemented transparent
reading of the {{gc.log}} file from Oak 1.6 by synthesising the full generation
number to the same value as the generation number.
[~frm], with this we should be mostly ready for bumping the segment version
number (OAK-6457)!? Subsequently we should implement a couple of ITs for
rolling upgrade feature.
> Implement rolling upgrade from Oak 1.6
> --------------------------------------
>
> Key: OAK-6531
> URL: https://issues.apache.org/jira/browse/OAK-6531
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: segment-tar
> Reporter: Michael Dürig
> Labels: migration, upgrade
> Fix For: 1.8, 1.7.7
>
>
> The segment format changes introduced for tail compaction (OAK-3349) must not
> require an explicit migration step. Instead there should be a rolling
> migration during normal operation.
> Things to consider:
> * Segments from Oak 1.6
> * Changes in tar index formats induced by the segment format changes
> * Changes in gc.log induced by the segment format changes
> * Required changes in the repository manifest and its interpretation
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
