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

Repeated upgrades

    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.1.7
    • Fix Version/s: 1.2.4, 1.3.3, 1.4
    • Component/s: upgrade
    • Labels:

      Description

      When upgrading from Jackrabbit 2 to Oak there are several scenarios that could benefit from the ability to upgrade repeatedly into one target repository.

      E.g. a migration process might look as follows:

      1. upgrade a backup of a large repository a week before go-live
      2. run the upgrade again every night (commit-hooks only handle delta)
      3. run the upgrade one final time before go-live (commit-hooks only handle delta)

      In this scenario each upgrade would require a full traversal of the source repository. However, if done right, only the delta needs to be written and the commit-hooks also only need to process the delta.

        Attachments

        1. incremental-upgrade-no-changes-mongo.png
          50 kB
          Julian Sedding
        2. incremental-upgrade-no-changes-tar.png
          61 kB
          Julian Sedding
        3. initial-upgrade-mongo.png
          64 kB
          Julian Sedding
        4. initial-upgrade-tar.png
          76 kB
          Julian Sedding
        5. OAK-2619.patch
          39 kB
          Julian Sedding
        6. OAK-2619-branch-1.0.patch
          45 kB
          Tomek Rękawek
        7. OAK-2619-v2.patch
          48 kB
          Julian Sedding

          Issue Links

            Activity

              People

              • Assignee:
                baedke Manfred Baedke
                Reporter:
                jsedding Julian Sedding
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: