ARROW-XXXX: [Java] Make StructVector.reallocValidityBuffer protected #12
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
Changes the access modifier of `reallocValidityBuffer` from package-private to protected. This allows subclasses to reallocate the validity buffer independently of the struct elements. Previously, expanding the validity buffer required a full vector reallocation, which could cause an `OversizedAllocationException` if the child data vectors were already near their capacity.
Author
|
Closed it because it was against main branch instead of dremio_27.0_20 |
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.
ARROW-XXXX: [Java] Make StructVector.reallocValidityBuffer protected
Changes the access modifier of
reallocValidityBufferfrom package-private to protected.This allows subclasses to reallocate the validity buffer independently of the struct elements. Previously,
expanding the validity buffer required a full vector reallocation, which could cause an
OversizedAllocationExceptionif the child data vectors were already near their capacity.