You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Stephan Matschinsky (JIRA)" <ji...@apache.org> on 2018/08/14 15:44:00 UTC
[jira] [Updated] (OAK-5193) Version tree may become inconsistent
after removing a version
[ https://issues.apache.org/jira/browse/OAK-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Matschinsky updated OAK-5193:
-------------------------------------
Attachment: OAK-5193-fix-v4.groovy
> 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.0.35, 1.2.21, 1.4.10, 1.5.14
> Reporter: Tomek Rękawek
> Assignee: Tomek Rękawek
> Priority: Major
> Fix For: 1.0.36, 1.2.22, 1.4.11, 1.5.15, 1.6.0
>
> Attachments: OAK-5193-fix-v2.groovy, OAK-5193-fix-v4.groovy, OAK-5193-fix.groovy, 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
(v7.6.3#76005)