Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-4308

Align the UpgradeTest#upgradeFrom10 to oak-segment-next

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              tomek.rekawek Tomek Rękawek

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment