[OAK-5112] oak-upgrade breaking versionStorage node when started with copy-versions=false

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.13
• Fix Version/s: 1.4.12, 1.5.14, 1.6.0
• Component/s: upgrade
• Assignee: Tomek Rękawek
• Reporter: Dominik Süß
• Created: 15/Nov/16 16:16
• Updated: 18/Mar/22 17:09
• Resolved: 21/Nov/16 12:37

Description

The attempt to sidegrade a repository and only keep the versionStorage of certain paths failed with a broken /jcr:system/jcr:versionStorage node when applying the following sequence:

java -jar oak-upgrade-1.6-SNAPSHOT.jar repository repository-temp  --copy-versions=false
java -jar oak-upgrade-1.6-SNAPSHOT.jar repository repository-temp  --copy-versions=true --include-paths=/path/requiring/versions

After first and second attempt the versionStorage node exists but has no primaryType. Startup works but fails when ever new nodes would be created underneath jcr:versionStorage.

The issue can be checked via oak-run console and running the following command

session.store.root.builder().getChildNode('jcr:system').getChildNode('jcr:versionStorage').getProperties()

//cc Tomek Rękawek, Alexandru Parvulescu

Issue Links

• is broken by: OAK-4175 Allow to skip the repository initialization in oak-upgrade
• Is contained by: OAK-5290 Backport the performance improvements for oak-upgrade from trunk