fix lm query fail when there are generated columns (#7386)#7397
fix lm query fail when there are generated columns (#7386)#7397ti-chi-bot wants to merge 1 commit intopingcap:release-7.1from
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
|
[REVIEW NOTIFICATION] This pull request has not been approved. To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by submitting an approval review. |
|
This cherry pick PR is for a release branch and has not yet been approved by release team. To merge this cherry pick, it must first be approved by the collaborators. AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
duplicate with #7387 |
This is an automated cherry-pick of #7386
Signed-off-by: Lloyd-Pottiger yan1579196623@gmail.com### What problem does this PR solve?
Issue Number: close #7383 close #7385
Problem Summary:
when there are generated columns, the size of
columns_to_readis less thantable_column_infos, due totable_column_infoscontains generated columns. So the order of columns changes, causing build filter incorrectly.Add generated columns to analyzer.
What is changed and how it works?
Check List
Tests
Side effects
Documentation
Release note