Remove WIP rust wrapper of fsspec input#166
Merged
kylebarron merged 1 commit intomainfrom Jan 28, 2025
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In kylebarron/arro3#61 and #15 I originally explored the possibility of passing an existing fsspec class (e.g. backed by s3fs) into Rust and using the fsspec class for data fetching. But I think this is not worth it. Rather, we should focus on the native store implementations provided by
object_store.Note that this does not remove the existing published fsspec adapter... the "export". It's still possible to use an obstore-backed class with python APIs that expect an fsspec-like class.
ref #15