Arrow: Fix oversized vector allocations in vectorized reads#17272
Open
ConeyLiu wants to merge 2 commits into
Open
Arrow: Fix oversized vector allocations in vectorized reads#17272ConeyLiu wants to merge 2 commits into
ConeyLiu wants to merge 2 commits into
Conversation
Contributor
Author
|
@wgtmac @RussellSpitzer @rdblue @nastra could you help review this when you are free? |
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.
Fix Arrow vector capacity allocation in vectorized reads.
The batch size was incorrectly multiplied by the estimated or fixed type width, causing oversized allocations. This change allocates variable-width, fixed-size binary, and INT96 vectors using the requested batch row count. Added a new UT to verify this.