feat: update arrow to 54 #9259
Draft
feat: update arrow to 54 #9259
+167
−178
Conversation
This file contains 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
|
Web viewer built successfully. If applicable, you should also test it:
Note: This comment is updated whenever you push a commit. |
|
A similar PR that is still open: |
timsaucer
added
🏹 arrow
timsaucer
force-pushed
the
feat/update-arrow-to-54
branch
from
4c472a5 to
8d0b6d3
Compare
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.
Related
Part of #3741
What
Now that lance, lancedb, and datafusion have all updated to arrow-54, this PR is aimed to upgrade rerun. The arrow update includes an update to pyo3, which deprecates some features and adds in additional requirements about having all python classes be
Sync, though this last point does not seem to impact our repo.