Problem/Motivation
EntityRevision:getIds() returns only ['revision_id'] and I think it should return ['id', 'revision_id'] so we can track both ids.
Currently Im migration an entity with ERR fields appling patch in #2809793: EntityReference migrate destination which creates a migration destination that extends from EntityRevision.
Thanks.
Proposed resolution
As stated in #5 only the vid is stored for revision migrations, if that were to change then it will break migrations of revisions from D6/D7. In the same comment heddn suggests that the langcode should be added to EntityRevision.php. This was added in #2921661: Add support to migrate multilingual revisions.
Remaining tasks
Close as wont fix?
Comment | File | Size | Author |
---|---|---|---|
#8 | 2820886-68.patch | 1.88 KB | heddn |
Comments
Comment #2
ruloweb CreditAttribution: ruloweb at Media.Monks commentedComment #3
heddnI think core revision support here intentionally intends to only track revisions, not a composite of revision and entity id. However, while reviewing this, I did note that we are not supporting revisions that are multi-lingual. Is that an issue that should be addressed?
We don't cover multi-lingual, because we aren't calling parent (rightfully so). But we do probably want to track the langcode on revisions, if the revision is multi-lingual. I've addressed that in #2809793-12: EntityReference migrate destination, but ideally CEB would have the multi-lingual code broken out into a protected function so I can just call it from ERR, rather than copy/pasting it.
Comment #4
ruloweb CreditAttribution: ruloweb at Media.Monks commentedand what is the idea behind this? if ERR calls parent:Ids() it wont be neccesary to solve id and language on each class that extends EntityRevision, as you did on #2809793-12: EntityReference migrate destination
Comment #5
heddnrevisions in D8 don't store a composite. Only the vid. This destination plugin was built for migrating in those values into core. If it returns a composite, it will break migrations of revisions from D6/D7. However, revisions do support mult-lingual. So we should suck in that data (me thinks).
Comment #7
heddnPatch doesn't apply.
Comment #8
heddnThe old patch wasn't what we wanted so I didn't bother re-rolling it.
Comment #9
mikeryanComment #10
mikeryanComment #14
quietone CreditAttribution: quietone as a volunteer commentedOn reviewing this it looks like it is a won't fix based on the comments in #5
Changing to NR to allow for replies.
Comment #15
heddnThis needs an IS update at the very least. We might need to track the langcode for revisions. Which is my last point in #5. Of course, that has BC implications.
Comment #16
quietone CreditAttribution: quietone as a volunteer commentedSince I'm doing a lot of multilingual.....
Comment #17
quietone CreditAttribution: quietone as a volunteer commentedThe proposed resolution points out that the langcode was added in #2921661: Add support to migrate multilingual revisions.
EntityRevision::getIds()
Comment #18
heddnSounds good.
Comment #19
quietone CreditAttribution: quietone as a volunteer commented