[OAK-2619] Repeated upgrades

• 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: doc-impacting
• Assignee: Manfred Baedke
• Reporter: Julian Sedding
• Created: 12/Mar/15 16:47
• Updated: 02/Mar/16 11:56
• Resolved: 15/Jul/15 21:44

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.

Issue Links

• blocks: OAK-2586 Support including and excluding paths during upgrade
• relates to: OAK-3242 Repeated upgrades in RepositorySidegrade