Feature / Add fsspec implementation for GCP storage in the runtime #379
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
… GCS arrow storage impl
…ringing them back
…m, use a context manager instead
… are not available
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.
The Arrow native FS implementation for GCS is not available on Windows, at least for some Windows versions. This PR adds an alternate implementation for GCS using the fsspec implementation and Arrow's fsspec wrapper.
Additionally, all the storage backends now support the "runtimeFs" property, which selects the storage implementation that is used in the runtime. The default is "auto", which selects the best available implementation for the current platform.