Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-6933

MigrateVersionWorkspacesToNewStructureTask fails in case where moved node has same name as the new generated parent

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 5.5, 5.5.1
    • Fix Version/s: 5.5.2
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Kromeriz 83
    • Story Points:
      5
    • Magnolia Release:
      5.5.2

      Description

      The versioned nodes are being moved to another location and the path of the current versioned node is /19, while the new path, being calculated from this versioned node uuid, is /19/33/44 (current uuid is like 19xxxx-33xxxx-44xxx-etc). While moving the former under the later we've met JCR consistency restriction, that the source path is an ancestor of destination path.
      And also set debug level for the warn messages to prevent flooding the log.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jsimak Jaroslav Simak
                Reporter:
                jsimak Jaroslav Simak
              • Votes:
                1 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Date of First Response: