mounter(ticdc): fix extend column info order to match the columns info (#8960) #8968
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automated cherry-pick of #8960
What problem does this PR solve?
Issue Number: close #8958
What is changed and how it works?
mounter's
datum2Column
method, reorder columns and columnInfos by the corresponding offset.model.RowChangedEvent
has a field namedColInfos
, it's the extended column infos, it's not reordered by thedatum2Columns
method, which makescolumns
andcolumnInfo
has the same column ID order, butcolumn
andColInfos
does not.ColInfos
should also be reordered by the datum2Columns` method, to make it has the same column ID order as the columns.For further refinement, Each
model.Column
should have fieldID
,FieldType
,IsPKHandle
, so that no need to keep theColInfo
at each event.Check List
Tests
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note