-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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: fix inconsistent schema between UnionAll and child operator (#30231) #30838
planner: fix inconsistent schema between UnionAll and child operator (#30231) #30838
Conversation
Signed-off-by: ti-srebot <[email protected]>
[REVIEW NOTIFICATION] This pull request has been approved by:
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. Reviewer can indicate their review by submitting an approval review. |
/run-all-tests |
@time-and-fate you're already a collaborator in bot's repo. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: d2c6c5b
|
/merge |
@ti-srebot: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. Instructions 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 ti-community-infra/tichi repository. |
/merge |
cherry-pick #30231 to release-5.0
You can switch your code base to this Pull Request by using git-extras:
# In tidb repo: git pr https://github.com/pingcap/tidb/pull/30838
After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
Issue Number: close #29705
Problem Summary:
The schema of the
UnionAll
is different from its children operators. Then the Union Exec returns an error.In this case, the
UnionAll
has one column but its childAggregation
has two. It's caused by an extra column is added toAggregation
in(*LogicalAggregation).PruneColumns()
.What is changed and how it works?
Add extra logic in
(*LogicalUnionAll).PruneColumns
to handle this case.When
UnionAll
finds its child has more columns, it will add the extra Projection to prune the extra column.About the additional changes in the test, please see the issue.
Check List
Tests
Side effects
Documentation
Release note