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 "Davide Giannella (JIRA)" <ji...@apache.org> on 2016/05/16 13:58:19 UTC
[jira] [Closed] (OAK-4308) Align the UpgradeTest#upgradeFrom10 to
oak-segment-next
[ https://issues.apache.org/jira/browse/OAK-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davide Giannella closed OAK-4308.
---------------------------------
Bulk close for 1.5.2
> 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-tar
> Reporter: Tomek Rękawek
> Priority: Minor
> Labels: migration, upgrade
> Fix For: 1.6, 1.5.2
>
>
> 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)