[OAK-6240] Sidegrade support for DocumentNodeStore to Secondary NodeStore

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.0, 1.8.0
• Component/s: documentmk, upgrade
• Labels: secondary-nodestore
• Assignee: Tomek Rękawek
• Reporter: Chetan Mehrotra
• Created: 19/May/17 04:09
• Updated: 10/Dec/18 17:41
• Resolved: 22/May/17 11:40

Description

Seondary NodeStore feature (OAK-4180) currently creates the secondary NodeStore upon initialization. This may take long time for existing repo. To simplify that we should add support in sidegrade to migrate an existing DocumentNodeStore setup to Secondary NodeStore

This would also allow us to use the sidegraded repository as a clone of existing repository with the advantage that it would support incremental updates. Currently if a repository is cloned it does not support incremental update as NodeState comparison is done based on default implementation (actual comparison) as it cannot make use of recordId or revision to optimize the diff to determine trees which are not changed between source and target

Issue Links

• breaks: OAK-6273 FilteringNodeStateTest#shouldHaveCorrectChildOrderProperty is failing
• is related to: OAK-7953 Test failure: JdbcToSegmentWithMetadataTest.validateMigration()
• relates to: OAK-4180 Use another NodeStore as a local cache for a remote Document store
• relates to: OAK-4626 Use oak-upgrade to initialize the DocumentMK local cache nodestore