[
https://issues.apache.org/jira/browse/OAK-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding updated OAK-2619:
--------------------------------
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:
# 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.
was:
When upgrading from Jackrabbit 2 to Oak there are several scenarios that could
benefit from the ability to merge content rather than overwrite it. Especially
in combination with OAK-2586, i.e. support to include/exclude selected paths
from the copy operation, merging can become very useful.
# Start vanilla product with an empty repo that writes some initial content,
then copy content from a Jackrabbit 2 repo into this instance
# Unify content from several Jackrabbit 2 repositories into a single Oak repo
# Copy all content 1 week before the actual migration, then merge in the diff
on migration day
Summary: Repeated upgrades (was: Support merging content during
upgrade)
> 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
>
> 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)
