-
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: create new column slice in PreparePossibleProperties #24342
Conversation
/cc @winoros |
cc @lzmhhh123 |
[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 |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: f16ed42
|
/merge |
/run-cherry-picker |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-5.0 in PR #24551 |
#26536) Co-authored-by: Mingcong Han <hanmingcong123@hotmail.com>
/label needs-cherry-pick-4.0 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-4.0 in PR #27929 |
What problem does this PR solve?
Issue Number: close #24281
Problem Summary:
Actually, the root cause of the issue is that the
LogicalAggregation.possibleProperties
is modified by(p *LogicalProjection) PreparePossibleProperties
, which is unexpected. Hence, the Aggregation generates a wrongrequiredProperty
for its child.What is changed and how it works?
What's Changed:
This PR just creates a new slice for the
possibleProperties
instead of a in-place update.Related changes
Check List
Tests
Release note