Implement GroupsAccumulator for map_agg UDAF#2
Closed
LiaCastaneda wants to merge 1 commit into
Closed
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Which issue does this PR close?
GroupsAccumulatorwhich different to the genericMapAggAccumulator, the difference is thatMapAggAccumulatoroperates row-by-row, converting each key/value toScalarValue, and DataFusion instantiates one per group.MapAggGroupsAccumulatorhandles all groups in a single instance, keeps data in columnar form, and uses a counting sort + arrow::compute::interleave to scatter rows into group order at emit time -- avoiding per-row scalar allocation.Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?