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 "Mark CHester (Jira)" <ji...@apache.org> on 2020/02/22 00:38:00 UTC

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=17042302#comment-17042302 ] 

Mark CHester edited comment on OAK-5193 at 2/22/20 12:37 AM:
-------------------------------------------------------------

Is this script expected to work on AEM 6.5 with Oak 1.10.2?  It appears to not work, and only outputs the Oak-run run modes in the log file.

I have this issue with running Version Purge, and this is the only information I can find on it.

Thanks!


was (Author: mchester):
Is this script expected to work on AEM 6.5 with Oak 1.10.2?  It appears to not work, and only outputs the Oak-run run modes in the log file.

I have this issue with running Version Purge, and this is the only information I can find on it.

> 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-v5.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
(v8.3.4#803005)