Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-6786

Existing version histories are not removed when using --include-versions=false

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • None
    • 1.8.0
    • upgrade
    • None

    Description

      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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            tomek.rekawek Tomek Rękawek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: