[Multi-stage] Support is_leaf_return_final_result agg option #14645
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.
Introduce
is_leaf_return_final_result
as an agg option, which leverages the query optionserverReturnFinalResultKeyUnpartitioned
introduced in #13208 to reduce the data transferred for aggregation group-by.When this option is set to true, LEAF aggregate will directly send final result to the FINAL aggregate. This is particular useful for DISTINCT_COUNT family aggregate when aggregated values are partitioned.
E.g.