-
Notifications
You must be signed in to change notification settings - Fork 1.5k
fix(sparksql): Default ignoreNulls to true for collect_set backward compatibility #16947
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
Closed
yaooqinn
wants to merge
2
commits into
facebookincubator:main
from
yaooqinn:fix/collect-set-default-ignore-nulls
+40
−32
Closed
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
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.
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.
Velox supports flushing during partial aggregation. When this happens, the intermediate results are left unaggregated, with the final aggregation step responsible for processing them. Could this cause any result issues?
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.
Good point! This is safe because:
When partial flushes (
toIntermediateis called), null filtering is already applied there:ignoreNulls_=true: null inputs become empty arrays (size=0), so the intermediate output contains no null elementsignoreNulls_=false:Base::toIntermediatewraps each value (including nulls) into[value]arraysFinal step receives pre-filtered data: Since
toIntermediatealready handles null filtering,addIntermediateResultsjust needs to merge arrays — usingaddValues(preserve everything) is correct for both cases.No behavior change: Before this fix, the final/intermediate nodes had
ignoreNulls_={false}by default, which also always usedaddValuesin the intermediate path. My change makes this explicit and removes the deadaddNonNullValuesbranch that was never reachable in the final step.