Fix the issue of unexpected results generated by groupBy queries when containing subqueries.#17598 #17599
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.
Fixes the issue of unexpected results generated by groupBy queries when containing subqueries#17598 .
Description
When processing groupby subqueries, it is necessary to finalize the returned results by the subqueries to support the aggregation operation of results by outer queries.
Fixed the bug that unexpected results generated by groupBy queries when containing subqueries.
When the groupBy subquery uses the longLast aggregator, the returned result is similar to Pair{lfs=xxx, lrs=xxx}, and it needs to be fanalized to support longSum or other aggregation operations in the outer groupBy query.
Before executing the outer aggregator, like longSum, the results of the subquery need to be transformed as follows:
Pair{lfs=xxx, lrs=###} -> ###
Key changed/added classes in this PR
GroupByQueryQueryToolChest.java
This PR has: