-
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: do not push down the aggregation function with correlated column (#21453) #21546
planner: do not push down the aggregation function with correlated column (#21453) #21546
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
/run-all-tests |
@Reminiscent you're already a collaborator in bot's repo. |
/run-all-tests |
@lzmhhh123 @eurekaka PTAL |
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
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 |
/run-all-tests |
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
cherry-pick #21453 to release-4.0
What problem does this PR solve?
Issue Number: close #21414
Problem Summary:
When an aggregation function with a correlated column pushed down, the correlated column will be incorrectly calculated as a null datum.
What is changed and how it works?
ContainCorrelatedColumn
to check if the expressions contain a correlated column.ContainCorrelatedColumn
toCheckAggCanPushCop
to prohibit aggFunc with a correlated column pushdown.Check List
Tests
Side effects
Some aggregation executor may not be pushed down.
Release note