-
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: do not return first row until the frame is completed. (#12480) #12660
executor: do not return first row until the frame is completed. (#12480) #12660
Conversation
Co-Authored-By: Zhuomin(Charming) Liu <lzmhhh123@gmail.com>
Sorry @SunRunAway, you don't have permission to trigger auto merge event on this branch. |
@SunRunAway please fill the PR description the same as the original PR #12480 |
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
…upstream-release-3.0
/run-all-tests |
cherry pick to release-3.1 in PR #12679 |
cherry pick to release-3.0 failed |
Automated cherry pick of #12480 on release-3.0.
What problem does this PR solve?
Fixes #12415.
What is changed and how it works?
In previous implementation,
windowExec
returns a chunk when a frame is fetched but not evaluated. After rewriting,windowExec
returns a chunk after a frame is finished evaluating.It makes the code simpler, and all the implementation of aggregation functions can reference the data in the frame. The bad side is it will increase the time of meeting first row.
I'll send a following PR(#12481) to revert the changes of copying data in #11678, if this is accepted by reviewers.
Check List
Tests
Code changes
Side effects
Related changes
Release note