SNOW-1886670 pin pyarrow #2163
Merged
SNOW-1886670 pin pyarrow #2163
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
sfc-gh-mkeller
force-pushed
the
mkeller/SNOW-1886670/pin-pyarrow
branch
from
2304a7a to
8158058
Compare
sfc-gh-mkeller
added
the
DO_NOT_PORT_CHANGES_TO_SP
sfc-gh-jszczerbinski
approved these changes
Jan 31, 2025
sfc-gh-mkubik
approved these changes
Jan 31, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Please answer these questions before submitting your pull requests. Thanks!
What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.
Fixes SNOW-1886670
Fill out the following pre-review checklist:
Please describe how your code solves the related issue.
We are seeing a strange bug on Azure Batch where
pyarrow==19.0.0is causing our nanoarrow implementation to not work. While we are investigating this issue I'm going to introduce a version pin to not allow users to break.This should be a short-term workaround only and the pin should not sick around for long!
(Optional) PR for stored-proc connector: