[jira] [Updated] (OAK-2619) Repeated upgrades
[ https://issues.apache.org/jira/browse/OAK-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-2619: -- Fix Version/s: 1.4 > 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 >Assignee: Manfred Baedke >Priority: Minor > Labels: doc-impacting > Fix For: 1.4, 1.2.4, 1.3.3 > > Attachments: OAK-2619-branch-1.0.patch, OAK-2619-v2.patch, > OAK-2619.patch, incremental-upgrade-no-changes-mongo.png, > incremental-upgrade-no-changes-tar.png, initial-upgrade-mongo.png, > initial-upgrade-tar.png > > > 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)
[jira] [Updated] (OAK-2619) Repeated upgrades
[ https://issues.apache.org/jira/browse/OAK-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Baedke updated OAK-2619: Fix Version/s: 1.2.4 > 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 >Assignee: Manfred Baedke >Priority: Minor > Labels: doc-impacting > Fix For: 1.2.4, 1.3.3 > > Attachments: OAK-2619-branch-1.0.patch, OAK-2619-v2.patch, > OAK-2619.patch, incremental-upgrade-no-changes-mongo.png, > incremental-upgrade-no-changes-tar.png, initial-upgrade-mongo.png, > initial-upgrade-tar.png > > > 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)
[jira] [Updated] (OAK-2619) Repeated upgrades
[ https://issues.apache.org/jira/browse/OAK-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomek Rękawek updated OAK-2619: --- Attachment: OAK-2619-branch-1.0.patch > 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 >Assignee: Manfred Baedke >Priority: Minor > Labels: doc-impacting > Fix For: 1.3.3 > > Attachments: OAK-2619-branch-1.0.patch, OAK-2619-v2.patch, > OAK-2619.patch, incremental-upgrade-no-changes-mongo.png, > incremental-upgrade-no-changes-tar.png, initial-upgrade-mongo.png, > initial-upgrade-tar.png > > > 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)
[jira] [Updated] (OAK-2619) Repeated upgrades
[ https://issues.apache.org/jira/browse/OAK-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Marth updated OAK-2619: --- Labels: doc-impacting (was: ) > 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 >Assignee: Manfred Baedke >Priority: Minor > Labels: doc-impacting > Fix For: 1.3.3 > > Attachments: OAK-2619-v2.patch, OAK-2619.patch, > incremental-upgrade-no-changes-mongo.png, > incremental-upgrade-no-changes-tar.png, initial-upgrade-mongo.png, > initial-upgrade-tar.png > > > 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)
[jira] [Updated] (OAK-2619) Repeated upgrades
[ https://issues.apache.org/jira/browse/OAK-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Baedke updated OAK-2619: Fix Version/s: 1.3.3 > 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 >Assignee: Manfred Baedke >Priority: Minor > Fix For: 1.3.3 > > Attachments: OAK-2619-v2.patch, OAK-2619.patch, > incremental-upgrade-no-changes-mongo.png, > incremental-upgrade-no-changes-tar.png, initial-upgrade-mongo.png, > initial-upgrade-tar.png > > > 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)
[jira] [Updated] (OAK-2619) Repeated upgrades
[ 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-v2.patch [~baedke], attached is a new patch which includes the changes to {{RepositoryUpgrade}}. I have also updated my github fork at https://github.com/code-distillery/jackrabbit-oak in case that's more convenient. > 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 >Assignee: Manfred Baedke >Priority: Minor > Attachments: OAK-2619-v2.patch, OAK-2619.patch, > incremental-upgrade-no-changes-mongo.png, > incremental-upgrade-no-changes-tar.png, initial-upgrade-mongo.png, > initial-upgrade-tar.png > > > 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)
[jira] [Updated] (OAK-2619) Repeated upgrades
[ https://issues.apache.org/jira/browse/OAK-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated OAK-2619: Attachment: initial-upgrade-tar.png initial-upgrade-mongo.png incremental-upgrade-no-changes-tar.png incremental-upgrade-no-changes-mongo.png > 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, > incremental-upgrade-no-changes-mongo.png, > incremental-upgrade-no-changes-tar.png, initial-upgrade-mongo.png, > initial-upgrade-tar.png > > > 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)
[jira] [Updated] (OAK-2619) Repeated upgrades
[ 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)
[jira] [Updated] (OAK-2619) Repeated upgrades
[ 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)
[jira] [Updated] (OAK-2619) Repeated upgrades
[ https://issues.apache.org/jira/browse/OAK-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated OAK-2619: Attachment: (was: OAK-2619-patch) > 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)