GH-692: Preserve nullability information while transfering DecimalVector and Decimal256Vector (#693) #3
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's Changed
This PR proposes to use the "from"
ValueVector's field while transferringDecimalVectorandDecimal256Vectorto preserve nullability information. This is to have similar behavior with all the other primitive value vectors. Note that theFieldTypeof the value vector has nullability information.Closes apache#692 .
(cherry picked from commit c29fcfc)