-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adapt to fsspec? #73
Comments
Sorry for the late response. Yes, that does indeed sound great to me. I will have a look this weekend and see how it can be adapted |
Given that datalake and blob now share an API, you may be able to do both in one :) I am happy to be involved in this, but I may disappear shortly on paternity leave. |
I agree, having fsspec compatibility would be great. I would also like it if the dask dependency could be optional, e.g., so I could use |
I am currently on vacation and will be back on 9th. Will continue working on it. |
ndeed, neither s3fs nor gcsfs depend on dask |
Hey everyone, |
Thanks for connecting @asiron . To you and everyone else on this thread: |
I had not noticed this new addition to the file-system landscape - thank you for producing this?
Would you be interested in adapting the code to be compatible with fsspec? This would mean better Dask integration for the future, and provide your implementation with many features shared with the other file-systems, such as advanced walk/glob, random-access files, transactional writes... and of course mean less duplication of code.
The text was updated successfully, but these errors were encountered: