[MGNLMIGRATION-190] Support persisting unfinished migration Created: 07/Dec/12 Updated: 01/Oct/13 Resolved: 13/Sep/13 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | None |
| Affects Version/s: | 1.2 |
| Fix Version/s: | 1.2.6, 2.0 |
| Type: | Task | Priority: | Major |
| Reporter: | Eric Hechinger | Assignee: | Robert Šiška |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ToDo_for_1_2_1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Task DoR: |
Empty
|
||||||||||||
| Date of First Response: | |||||||||||||
| Description |
|
Currently the session is saved, after each migration task, in case of success. "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. |
| Comments |
| Comment by Roman Kovařík [ 29/Mar/13 ] |
|
Saving the session only after the task is not real for big project because of huge amount of nodes in the memory. See |
| Comment by Robert Šiška [ 13/Sep/13 ] |
|
The saving during of task is disabled by default, but can be allowed by setting |
| Comment by Jan Haderka [ 13/Sep/13 ] |
|
Can we change name of the property controlling saving to something more self explanatory? Maybe something like "savePartiallyMigratedContent"? |
| Comment by Robert Šiška [ 16/Sep/13 ] |
|
Changed property name from magnolia.migration.sessionSaving to magnolia.migration.savePartiallyMigratedContent. |