[
https://issues.apache.org/jira/browse/OAK-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek Rękawek updated OAK-5193:
-------------------------------
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.
!version-histories.png!
They should be merged together, instead.
was:
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.
> Version tree may become inconsistent after removing a version
> -------------------------------------------------------------
>
> Key: OAK-5193
> URL: https://issues.apache.org/jira/browse/OAK-5193
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Affects Versions: 1.2.20, 1.0.35, 1.4.10, 1.5.14
> Reporter: Tomek Rękawek
> Assignee: Tomek Rękawek
> Attachments: version-histories.png
>
>
> 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.
> !version-histories.png!
> They should be merged together, instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
