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 "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2017/10/05 17:17:00 UTC

[jira] [Resolved] (OAK-6786) Existing version histories are not removed when using --include-versions=false

     [ https://issues.apache.org/jira/browse/OAK-6786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomek Rękawek resolved OAK-6786.
--------------------------------
    Resolution: Duplicate

Duplicate of OAK-6633. Closing.

> Existing version histories are not removed when using --include-versions=false
> ------------------------------------------------------------------------------
>
>                 Key: OAK-6786
>                 URL: https://issues.apache.org/jira/browse/OAK-6786
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: upgrade
>            Reporter: Tomek Rękawek
>             Fix For: 1.8
>
>
> For a partial migration, if the destination content already exists and have version histories, when using {{\-\-include-versions=false}}, the existing histories should be removed from target. However, it's not the case.
> The reason is that the VersionableEditor is only invoked for the modified content. If the content is the same both on the source and the target, the VersionableEditor won't be called and the version histories won't be removed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)