Uploaded image for project: 'Magnolia DAM Module'
  1. Magnolia DAM Module
  2. MGNLDAM-51

MoveUploadedContentToDamMigrationTask store's fileName and extension redundantly

    XMLWordPrintable

Details

    • Task
    • Resolution: Won't Fix
    • Critical
    • None
    • 1.0
    • None
    • None

    Description

      Reviewing MGNLDAM-4 (and subtasks) revealed that MigrationTasks stores fileName and extension on the AssetNode and on the ResourceNode.
      Next to the fact we're "wasting" memory this is very likely to cause problems as we cannot guarantee they'll always be kept in synch.
      We should investigate where we need which of these properties and then drop them from the AssetNode or the ResourceNode.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              ehechinger Eric Hechinger
              dlipp Daniel Lipp
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoR