-
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: stream agg should not be pushed to double read #12443
Conversation
} else { | ||
partialAgg.SetChildren(cop.indexPlan) | ||
cop.indexPlan = partialAgg | ||
if cop.extraHandleCol == nil { |
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.
Could you please add a comment here to explain the reason? I think it may be hard to understand without this PR's description.
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.
added.
Codecov Report
@@ Coverage Diff @@
## master #12443 +/- ##
================================================
- Coverage 79.8628% 79.6481% -0.2147%
================================================
Files 461 461
Lines 103803 101465 -2338
================================================
- Hits 82900 80815 -2085
- Misses 14813 14827 +14
+ Partials 6090 5823 -267 |
Please fix the explain tests. |
Co-Authored-By: Zhuomin(Charming) Liu <lzmhhh123@gmail.com>
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 |
LGTM |
/run-all-tests |
@winoros merge failed. |
/merge |
/run-all-tests |
cherry pick to release-2.1 failed |
cherry pick to release-3.1 failed |
cherry pick to release-3.0 failed |
For the following two reason, we should not push stream agg down to double read - The aggregate will lost the handle information - There's no sort operator. The second read is ordered with pk, not by index.
For the following two reason, we should not push stream agg down to double read - The aggregate will lost the handle information - There's no sort operator. The second read is ordered with pk, not by index.
It seems that, not for sure, we failed to cherry-pick this commit to release-2.1. Please comment '/run-cherry-picker' to try to trigger the cherry-picker if we did fail to cherry-pick this commit before. @winoros PTAL. |
What problem does this PR solve?
For the following two reason, we should not push stream agg down to double read
What is changed and how it works?
Disable it.
Check List
Tests
Related changes
Release note