[SPARK-52678] Update ArrowReader.swift with GH-54
#207
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
|
cc @viirya and @peter-toth |
viirya
approved these changes
Jul 3, 2025
|
Thank you, @viirya . Merged to main. |
|
Late LGTM. |
|
Thank you, @peter-toth . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 update
ArrowReader.swiftwithGH-54.Please note that we cannot use
Apache Arrow Swiftdirectly yet becauseDecimal.Decimal128arrow#46628GRPC Swiftwhile we useGRPC Swift 2.Why are the changes needed?
To be ready for the upstream release because
v21.0.0-rc0tag is created.According to the release notes, this seems to be the only one which needs to catch up.
Does this PR introduce any user-facing change?
No behavior change because this is a refactoring to suppress warning messages.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.