[OAK-5193] Version tree may become inconsistent after removing a version

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.35, 1.2.21, 1.4.10, 1.5.14
• Fix Version/s: 1.0.36, 1.2.22, 1.4.11, 1.5.15, 1.6.0
• Component/s: jcr
• Assignee: Tomek Rękawek
• Reporter: Tomek Rękawek
• Created: 30/Nov/16 12:13
• Updated: 08/Sep/21 14:41
• Resolved: 01/Dec/16 12:12

Description

When a version is removed, its predecessors and successors are connected together, to keep the version tree consistent. However, if the removed version predecessor has its own successors, they are replaced with the removed version successors. Similarly, if the removed version successor has its own predecessors, they'll be replaced with the removed version predecessors.

They should be merged together, instead.

Issue Links

• relates to: OAK-9567 Avoid NullPointerException in ReadWriteVersionManager.removeVersion