-
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
executor: fix update panic on join having statement (#23554) #23575
executor: fix update panic on join having statement (#23554) #23575
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
/run-all-tests |
@lzmhhh123 you're already a collaborator in bot's repo. |
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
@eurekaka: In response to this:
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. |
/lgtm |
/lgtm |
[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 writing |
@lzmhhh123 Please fix the failed test in the |
/run-all-tests |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: d68e2ce
|
@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. |
cherry-pick #23554 to release-4.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/23575
After apply modifications, you can push your change to this PR via:
Signed-off-by: lzmhhh123 lzmhhh123@gmail.com
What problem does this PR solve?
Issue Number: close #23553
What is changed and how it works?
How it Works: when pruning projection, for the two continuous projections, the top one has been pruning, but the below one has a different schema. Then it causes their parent operator recognising some schema columns as unused columns, then cause update panic.
Related changes
Check List
Tests
Side effects
Release note