[OAK-4529] DocumentNodeStore does not have a repository software version range check

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.31, 1.2.14, 1.4.4, 1.5.4
• Fix Version/s: 1.7.0, 1.8.0
• Component/s: core, documentmk
• Assignee: Marcel Reutegger
• Reporter: Ian Boston
• Created: 04/Jul/16 09:13
• Updated: 24/Jul/19 14:01
• Resolved: 21/Mar/17 10:44

Description

DocumentNodeStore does not currently check which software version the persisted repository it is connecting to was created with or last updated. There is a risk that if the versions are incompatible the repository may be damaged.

Somewhere in the repository, the version of the software that created it, and the versions that written to it should be stored. In the case of TarMK this information could be on local disk near the TarMK files. In the case of a DocumentMK implementation, the information should be stored in the "database" itself.

When a DocumentNodeStore instance connects it should: check the versions stored in the repository then check the versions are within a compatible range and refuse to start if not.

When a DocumentNodeStore writes to a repository, it should add its version to the list of versions that have updated the repository.

This check behaviour should be active in full Oak or any utilities (eg oak-run).

Issue Links

• blocks: OAK-3287 DocumentMK revision GC
• is related to: OAK-7703 Format version handling on upgrade