Skip to content
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

fsspec integration #690

Open
martindurant opened this issue Apr 24, 2024 · 2 comments
Open

fsspec integration #690

martindurant opened this issue Apr 24, 2024 · 2 comments

Comments

@martindurant
Copy link

I was only recently made aware of this library. Fsspec has some similar concerns, but is primarily used for interacting with remote storage systems, whereas most of the FS-like targets here are local file containers. Would you like to provide a shim such that fsspec.filesystem or fsspec.open can deal with a dissect target filesystem type? It could have a benefit to you, maybe opening a filesystem container file in a remote store.

I am also interested in the FUSE integration. fsspec also has this, but it is flaky, experimental and rarely used. Perhaps the solution here is more robust, and all fsspec filesystem types could be exposed.

@martindurant
Copy link
Author

martindurant commented Apr 24, 2024

cc @mxmlnkn of ratarmount

@Schamper
Copy link
Member

Schamper commented May 6, 2024

Hi @martindurant, thanks for reaching out! Apologies for the delayed response, I also saw the other thread where Dissect was mentioned and wanted to give an in-depth reply there, but some things came up and I just couldn't get around to it yet. When I have some more time I'd still like to elaborate some of our decisions and goals in further detail there.

To give a short response, this looks interesting to us and something we'd be interested in exploring. Could you perhaps give a short overview of the necessary tasks or some API references so we can make an estimate on how much work this would be?

FYI, our FUSE implementation isn't flawless (or particularly fast), but it does get used very heavily and seems to be pretty stable overall.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants