querier: Implement child-to-root fragment execution model #7019
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…execution model Signed-off-by: rubywtl <[email protected]>
rubywtl
force-pushed
the
querier/child-root-execution
branch
from
d03d734 to
88e1346
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does:
This PR implements fragment execution support in queriers following a child-to-root execution model. Queriers can now process logical plan fragments distributedly via the new querier gRPC interface while maintaining proper execution order: child fragments are executed first, with their partial results made available for parent fragments to consume. This execution pattern ensures data dependencies are satisfied and enables proper coordination between distributed fragments.
Which issue(s) this PR fixes:
related to Distributed Query Execution proposal
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]