[
https://issues.apache.org/jira/browse/OAK-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257990#comment-15257990
]
Alex Parvulescu commented on OAK-4308:
--------------------------------------
bq. moving the test to the upgrade module seems to make a lot of sense.
+1
> Align the UpgradeTest#upgradeFrom10 to oak-segment-next
> -------------------------------------------------------
>
> Key: OAK-4308
> URL: https://issues.apache.org/jira/browse/OAK-4308
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: jcr, segment-next
> Reporter: Tomek Rękawek
> Priority: Minor
> Labels: migration, upgrade
> Fix For: 1.6
>
>
> Test case {{UpgradeTest#upgradeFrom10}} in the {{oak-jcr}} module unpacks an
> archived TarMK repository in the Oak 1.0 format and tries to run the current
> oak-segment on top on that. It also validates whether all the data are in
> place.
> This works, because the oak-segment code automatically detects the old
> repository format and upgrades it in-place, without any user action.
> However, after changing this test to use the oak-segment-next it'll break,
> because the upgrade path for the new repository code is more complex - it
> requires invoking the oak-upgrade manually, to sidegrade the data (as in
> OAK-4260).
> We should move this test to the oak-upgrade module and modify it a bit, so
> the data are sidegraded before the repository is validated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
