Closed (fixed)
Project:
Drupal core
Version:
8.3.x-dev
Component:
migration system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
14 Oct 2016 at 01:42 UTC
Updated:
17 Nov 2016 at 15:15 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
heddnComment #3
ada hernandez commentedI have added a patch with the commentaries in migration templates.
Comment #4
heddnThe comment for UID should be closer to the uid field. Can we move the uid field up higher so it is right next to the fid?
Same applies here for uid. Can we move it higher so the comment applies more closely?
And here. Move uid closer.
And here.
And here.
I don't think it makes sense to remove this one. The vid isn't a numeric identifier for taxonomy vocabularies.
I think this is similar to vocabularies. We don't want to remove it here.
I think this is similar to vocabularies. We don't want to remove it here.
Comment #5
ada hernandez commented@heddn thanks for your feedback, I have removed the commentaries unnecessary.
Comment #6
ada hernandez commentedComment #8
ada hernandez commented@heddn now is the correct patch :).
Comment #9
mikeryanThe uid mapping should not be removed. If IDs are not preserved, the uid mapping should use the migration plugin instead of a straight mapping - but we have another issue to do that in general.
Ditto, uid mapping should not be removed.
Ditto.
Ditto.
Ditto, and etc. for the rest (I need to leave atm, haven't reviewed the rest...).
Comment #10
ada hernandez commented@mikeryan thanks. I have removed the uid for templates migration now.
Comment #11
mikeryanSo, to be clearer and more complete than my dashed-off review yesterday - we only need to remove ID mappings from a migration when they are the primary ID of the entity being created by that migration. There are a number of subsidiary migrations which do not create entities themselves, where the primary ID is of an existing entity being updated - that ID must be mapped for the right entity to be updated.
With the changes below, I'll be ready to RTBC this. Thanks!
Actually, this one should not be removed, because it is properly mapping to the migrated nid (whether nids were preserved or not).
Similar to my previous uid reference - this must be mapped, and really should be using the migration plugin to work when IDs are not preserved, but we have a separate issue for that.
Ditto.
Comment #12
ada hernandez commented@mikeryan thank you very much, I'll work in that
Comment #13
ada hernandez commentedI updated the patch I removed the commentary for the ID must be mapped now I think this is correct.
Comment #14
mikeryanThat does it, thanks!
Comment #15
ada hernandez commentedIt is a pleasure to help community
Comment #16
alexpottWouldn't you also have to comment the vid for the node migrations? (I might be wrong - but I think I had to do this on a recent migration).
Also aren't we missing comments?
Comment #17
mikeryanAh, right, should have caught that, thanks!
Comment #18
ada hernandez commentedHi everyone, it did the changes for node templates
Comment #19
ada hernandez commentedComment #20
mikeryanThere's also alexpott's second comment:
I.e., we need to also document this for the cid mappings in d6_comment and d7_comment.
Comment #21
ada hernandez commentedOh!, ok thanks
Comment #22
ada hernandez commentedI have added commentaries for comment migration template
Comment #23
mikeryanThanks!
Comment #24
alexpottCommitted and pushed f1b66f3 to 8.3.x and d76893e to 8.2.x. Thanks!
Adding to 8.2.x because this is just documentation.