-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
planner, executor: eliminate extra columns introduced by OrderBy upon Union #8290
Conversation
Hi contributor, thanks for your PR. This patch needs to be approved by someone of admins. They should reply with "/ok-to-test" to accept this PR for running test automatically. |
/run-all-tests |
/run-all-tests |
7065750
to
274adae
Compare
… introduced by OrderBy upon Union
274adae
to
137230d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for contributing. please add a unit test in planner/core package for keeping test's coverage.
main changes LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
/run-all-tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@AndrewDi It seems that we should cherry-pick this to release-2.1 and release-2.0? |
What problem does this PR solve?
fix issue #8189 and issue #8199
What is changed and how it works?
When a
SELECT
statement containsUNION
andORDER BY
cause contains select statement,TiDB will generate extra columns, so I addLogicalProjection
when building union LogicalPlan to eliminate generated extra columns.Check List
Tests
Code changes
Side effects
Related changes