[ https://issues.apache.org/jira/browse/OAK-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Sedding updated OAK-2619: -------------------------------- Attachment: OAK-2619.patch Replaced old patch. For additional context take a look at the changes in my github fork\[0\]. \[0\] https://github.com/apache/jackrabbit-oak/compare/trunk...code-distillery:trunk > Repeated upgrades > ----------------- > > Key: OAK-2619 > URL: https://issues.apache.org/jira/browse/OAK-2619 > Project: Jackrabbit Oak > Issue Type: New Feature > Components: upgrade > Affects Versions: 1.1.7 > Reporter: Julian Sedding > Priority: Minor > Attachments: OAK-2619.patch > > > 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: > # upgrade a backup of a large repository a week before go-live > # run the upgrade again every night (commit-hooks only handle delta) > # 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)