-
Notifications
You must be signed in to change notification settings - Fork 2.4k
perf: Avoid copying when materializing output in OrderedPartialAggregateStream #25312
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
2010YOUY01
wants to merge
3
commits into
apache:main
Choose a base branch
from
2010YOUY01:faster-output-order-partial-aggr
base: main
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.
+271
−207
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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.
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.
[P2] Preserve dictionary capacity limits before materializing the whole range
Materializing all completed groups before slicing can exceed a dictionary's key capacity even when every input batch is valid. I reproduced this with
GROUP BY (sort_col, nested), wherenestedisStruct<Dictionary<Int8, Utf8>>, input is ordered only onsort_col, and three valid 64-row batches contain 192 distinct nested dictionary values under the same sort key. Withbatch_size=32, base returns all expected groups; head panics inRowsGroupColumn::rows_to_arraywithdictionary re-encode during emit: ArrowError(DictionaryKeyOverflowError, ...).Both EOF and a subsequent sort-key boundary trigger it. Widening the dictionary keys to Int16 makes the head cases pass. A second reproducer with ordinary integer grouping keys and
ARRAY_AGG(Dictionary<Int8, Utf8>)also passes on base and returnsDictionaryKeyOverflowErroron head during state materialization.Please retain bounded materialization for key/state encodings that cannot represent the whole completed range in one Arrow array, or emit multiple independently representable batches. Slicing after constructing the combined array is too late to avoid the overflow.
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.
Similar to #25312 (comment) , we should be able to avoid slicing in the long term.
Though I don't fully get the issue for dictionary keys, so I don't know if there is something to fix elsewhere to better address the root cause.