-
Notifications
You must be signed in to change notification settings - Fork 3.9k
[fix](local shuffle) Require hash input for distinct finalize agg without group keys #66570
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
Open
924060929
wants to merge
1
commit into
apache:master
Choose a base branch
from
924060929:fix/agg-finalize-distinct-hash
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+302
−20
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
[P1] Do not create a zero-key HASH exchange for direct multi-distinct calls
This predicate also matches a directly called scalar multi_distinct_count(col). That function has isDistinct=false, so SplitAggWithoutDistinct builds a two-phase LOCAL aggregate with no partitionExpressions; over a non-hash scan both the child distribution list and grouping list are empty. With the default LE setting this branch now reaches requireHash(), and getLocalExchangeDistributeExprs() supplies zero expressions. BE's hash partitioner initializes every row to hash 0, so the resulting FE-planned HASH exchange sends the whole input to channel 0, collapsing the partial aggregate to one task per BE and concentrating its distinct state in one task. BE's own AggSinkOperatorX sees empty _partition_exprs on this path and uses the base requirement instead. Please base the LOCAL decision on a non-empty effective key (while retaining the keyed finalize fix), and add a direct-function plan case that rejects a zero-expression HASH exchange.