Skip to content

Conversation

@LuciferYang
Copy link
Contributor

@LuciferYang LuciferYang commented May 14, 2025

Copy link
Member

@dongjoon-hyun dongjoon-hyun left a comment

Choose a reason for hiding this comment

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

Nice! Thank you for tracking this, @LuciferYang .

@LuciferYang LuciferYang changed the title Test Arrow Java 18.3.0 [SPARK-52132][BUILD] Upgrade arrow-java to 18.3.0 May 14, 2025
@LuciferYang LuciferYang marked this pull request as ready for review May 14, 2025 14:34
Copy link
Member

@dongjoon-hyun dongjoon-hyun left a comment

Choose a reason for hiding this comment

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

+1, LGTM. Thank you, @LuciferYang and @yaooqinn .
Merged to master.

@LuciferYang
Copy link
Contributor Author

Thank you @dongjoon-hyun and @yaooqinn

@LuciferYang LuciferYang deleted the arrow-java-18.3.0 branch May 19, 2025 05:07
yhuang-db pushed a commit to yhuang-db/spark that referenced this pull request Jun 9, 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 apache#50892 from LuciferYang/arrow-java-18.3.0.

Authored-by: yangjie01 <[email protected]>
Signed-off-by: Dongjoon Hyun <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants