Skip to content

GH-692: Preserve nullability information while transfering DecimalVector and Decimal256Vector - #693

Merged
jbonofre merged 2 commits into
apache:mainfrom
bodduv:decimal-nullability
Apr 3, 2025
Merged

GH-692: Preserve nullability information while transfering DecimalVector and Decimal256Vector#693
jbonofre merged 2 commits into
apache:mainfrom
bodduv:decimal-nullability

Conversation

@bodduv

Copy link
Copy Markdown
Contributor

What's Changed

This PR proposes to use the "from" ValueVector's field while transferring DecimalVector and Decimal256Vector to preserve nullability information. This is to have similar behavior with all the other primitive value vectors. Note that the FieldType of the value vector has nullability information.

Closes#692 .

@lidavidmlidavidm changed the title Preserve nullability information while transfering DecimalVector and Decimal256VectorGH-692: Preserve nullability information while transfering DecimalVector and Decimal256VectorMar 27, 2025
@lidavidmlidavidm added this to the 18.3.0 milestone Mar 27, 2025
@github-actions

This comment has been minimized.

@lidavidmlidavidm added the bug-fix PRs that fix a big. label Mar 27, 2025
@bodduv

bodduv commented Mar 27, 2025

Copy link
Copy Markdown
ContributorAuthor

@lidavidm Thank you! Looks like the Dev PR Github workflow could not update milestone for the linked issue.

Comment threadvector/src/main/java/org/apache/arrow/vector/Decimal256Vector.java Outdated
Comment threadvector/src/main/java/org/apache/arrow/vector/DecimalVector.java Outdated
@bodduv
bodduv requested a review from jbonofreApril 1, 2025 08:24

@jbonofrejbonofre left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@lidavidm@kou do you mind to take a look ? If good, I propose to merge.

@jbonofre
jbonofre merged commit c29fcfc into apache:mainApr 3, 2025
bodduv added a commit to dremio/arrow-java that referenced this pull request Apr 4, 2025
…malVector and Decimal256Vector (apache#693)
## What's Changed
This PR proposes to use the "from" `ValueVector`'s field while
transferring `DecimalVector` and `Decimal256Vector` to preserve
nullability information. This is to have similar behavior with all the
other primitive value vectors. Note that the `FieldType` of the value
vector has nullability information.
Closesapache#692 .
(cherry picked from commit c29fcfc)
bodduv added a commit to dremio/arrow-java that referenced this pull request Apr 4, 2025
…malVector and Decimal256Vector (apache#693) (#3)
This PR proposes to use the "from" ValueVector's field while transferring DecimalVector and Decimal256Vector to preserve nullability information. This is to have similar behavior with all the other primitive value vectors. Note that the FieldType of the value vector has nullability information.
Closesapache#692 .
(cherry picked from commit c29fcfc)
dongjoon-hyun pushed a commit to apache/spark that referenced this pull request May 15, 2025
### What changes were proposed in this pull request?
This pr aims to upgrade `arrow-java` from 18.2.0 to 18.3.0.
### Why are the changes needed?
The new version bring some bug fixes, like:
- apache/arrow-java#627
- apache/arrow-java#654
- apache/arrow-java#656
- apache/arrow-java#693
- apache/arrow-java#705
- apache/arrow-java#707
- apache/arrow-java#722
In addition, the new version introduces a cascading upgrade for flatbuffers-java([ from 24.3.25 to 25.1.24 ](apache/arrow-java#600))
the full release note as follows:
- https://github.com/apache/arrow-java/releases/tag/v18.3.0
### Does this PR introduce _any_ user-facing change?
No
### How was this patch tested?
- Pass GitHub Acitons
### Was this patch authored or co-authored using generative AI tooling?
No
Closes#50892 from LuciferYang/arrow-java-18.3.0.
Authored-by: yangjie01 <yangjie01@baidu.com>
Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
timhurskidremio pushed a commit to timhurskidremio/dremio-arrow-java that referenced this pull request Dec 5, 2025
…malVector and Decimal256Vector (apache#693)
## What's Changed
This PR proposes to use the "from" `ValueVector`'s field while
transferring `DecimalVector` and `Decimal256Vector` to preserve
nullability information. This is to have similar behavior with all the
other primitive value vectors. Note that the `FieldType` of the value
vector has nullability information.
Closesapache#692 .
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug-fixPRs that fix a big.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[arrow-vector] Zero-copy transfer of DecimalVector and Decimal256Vector is losing nullability information

3 participants

@bodduv@jbonofre@lidavidm