Uploaded image for project: 'Migration 4.4 to 4.5 (closed)'
  1. Migration 4.4 to 4.5 (closed)
  2. MGNLMIGRATION-190

Support persisting unfinished migration

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.2
    • Fix Version/s: 1.2.6, 2.0
    • Component/s: None
    • Labels:

      Description

      Currently the session is saved, after each migration task, in case of success.
      Based on the following remark the way to handle session.save() should be first discussed and probably review.

      "Well any kind of save within task is violation of contract for task since it can't be rolled back and reexecuted by install manager so it needs to be documented in the task. Plus sessions are saved by install manager after execution of all tasks for given module successfully. From what yo usay above i still don't see reason to force the save per task."

      Just on additional remark.
      The tasks support to be reexecuted even if the migration already took place.

        Checklists

        Acceptance criteria

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                rsiska Robert Šiška
                Reporter:
                ehechinger Eric Hechinger
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:
                  Date of First Response:

                    Checklists

                    Task DoR