[WIP][ML] Avoid VectorUDT deserialization in Summarizer - #57967
Draft
zhengruifeng wants to merge 1 commit into
Draft
[WIP][ML] Avoid VectorUDT deserialization in Summarizer#57967zhengruifeng wants to merge 1 commit into
zhengruifeng wants to merge 1 commit into
Conversation
zhengruifeng
changed the title
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.
What changes were proposed in this pull request?
Update the DataFrame Summarizer aggregate to consume vectors from their internal SQL
representation. A nonzero iterator reads dense values and sparse index-value pairs directly from
Catalyst ArrayData. Count-only summaries avoid iterating over vector values.
Why are the changes needed?
Summarizer currently calls VectorUDT.deserialize for every input row. This copies the dense values
array, or both sparse indices and values arrays, and then allocates a Vector wrapper before
aggregation. Reading the internal row directly avoids these per-row copies and Vector allocation.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
The existing SummarizerSuite covers dense, sparse, weighted, count-only, and multi-metric summary
behavior.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Codex (GPT-5)