[SPARK-51801][BUILD] Upgrade ORC Format to 1.1.0 #50588
Closed
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
16 tasks
dongjoon-hyun
force-pushed
the
SPARK-51801
branch
from
7aaf2d9 to
b531be6
Compare
dongjoon-hyun
changed the title
Member
Author
|
All tests passed. This PR is ready. |
Member
Author
|
Could you review this PR when you have some time, @yaooqinn ? |
Member
Author
|
Oh, thank you so much, @yaooqinn ! |
16 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 changes were proposed in this pull request?
This PR aims to upgrade Apache ORC Format to 1.1.0 from 1.1.0 for Apache Spark 4.1.0.
Why are the changes needed?
Apache ORC Format v1.1.0 is released on 2025-04-18.
To bring the latest feature and bug fixes.
protobuf-javato 3.25.5 orc-format#19Does this PR introduce any user-facing change?
No, there is no behavior change.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.