[MAGNOLIA-6694] Meta data conversion modifies node status Created: 14/Jun/16 Updated: 21/Jun/16 Resolved: 20/Jun/16 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.4.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Lars Fischer | Assignee: | Robert Šiška |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | metadata, migration, quickwin, tasks | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Patch included: |
Yes
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Epic Link: | Do not use MgnlPropertySetting decorator on update |
| Sprint: | Kromeriz 49 |
| Story Points: | 0 |
| Description |
|
The conversion of the old node meta data structure to the new mixin format *in a migration context * causes the state of nodes to be modified. This prevents having the same activation states as on the initial systems. The flow during migration is as follows:
—> MgnlPropertySettingContentDecorator.ChangeLastUpdateDateOp.doExec() to add nodes to dirtyOps
if (periodicSaves && nodesProcessed % PERIODIC_SAVE_FREQUENCY == 0) { node.getSession().save(); }—> MgnlPropertySettingContentDecorator. MgnlPropertySettingSessionWrapper.save() if (session.nodeExists(dirty.getPath())) { Regarding to Jan H. the node must be unwrapped before further processing to prevent the unwanted modifications. See the attached patch file about how to unwrap the node. |