Replies: 1 comment
-
|
There are certainly example for some backends that do this kind of thing (ftp, ssh, github come to mind). In those cases, we are making use of established URL patterns - although with some invention also for the case of github. How to formulate this kind of thing might be tricky - we'd be making a pattern that doesn't exist anywhere else. I think your idea for chaining isn't a bad one: passing that URL to fsspec.open would result in these kwargs going to S3FileSystem: which is essentially the information you are after. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is there any appetite for embedding host/endpoint information within fsspec URLs? Currently, protocols like
s3://or evenhf://can be ambiguous as they may refer to local servers as opposed to their more popular web counterparts.I know I can configure local variables to point to the server of my choice (via AWS config file, environment variables, or even local Python variables) but I'd prefer to have this information captured in the URL itself. Some ideas for how this could be achieved:
s3://bucket/path?host=my-minio-server.com&scheme=httpss3://[email protected]/paths3://bucket/path::https://my-minio-server.comI haven't seen anyone else asking for this, so I doubt this will go anywhere, but I'd be interested in finding other people that also care about this problem.
Beta Was this translation helpful? Give feedback.
All reactions