Merged
Conversation
Contributor
Author
Member
|
Hi. Thank you. There are errors in CI. Apparently, we just need to bump to 58 in |
Contributor
Author
|
Yeah... need's fix. Will update this. |
Contributor
Author
|
@Expurple all good. |
Expurple
approved these changes
Mar 14, 2026
🎉 Released In 2.0.0-rc.38 🎉Huge thanks for the contribution! |
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
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.


PR Info
Naively updates arrow to arrow 58.
Local tests are passing, so I though it should be fine.
New Features
No more duplicate issues with up to date Cargo crates.
Arrow 58 has explicit feature for
asyncforarrow-arrays, which enablesfutures.So, there might be a slight change in feature flags for proper async parquet processing.
Bug Fixes
Arrow 58 deprecates older API's, so I presume that there should be no regression.
Breaking Changes
None found.
Changes
None meaningful.