-
Notifications
You must be signed in to change notification settings - Fork 867
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
object_store: Support container@account.dfs.core.windows.net/path
URL style for az
protocol
#7046
Comments
container@account.dfs.core.windows.net/path
URL style for az
protocolcontainer@account.dfs.core.windows.net/path
URL style for az
protocol
This seems fine to me and should be a relatively straightforward change to MicrosoftAzureBuilder::parse_url |
As an extension to the above feature request, I can see that
However, it would be excellent if these could be extended to support the following generic structure:
where:
This matches the URL structure used by Microsoft's AzCopy tool. |
The only addition you're suggesting is the |
Also in the documentation, it lists
But not
My goal is to be able to use the following in Polars:
But I've tried, and it didn't seem to work. When I checked the I also saw in the documentation that other URL schemes were specified as supporting the |
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
In adlfs (fsspec), there are two valid conventions for specifying a canonical path to Azure Data Lake Gen2 storage, including the account name:
While
object_store
supports both theaz
andabfs
protocols, it does not support specifying the account in the URL for theaz
protocol.However, it does support this for the
abfs
protocol.Describe the solution you'd like
I would like to be able to use the following URL convention with
object_store
, which improves compatibility withadlfs
:Describe alternatives you've considered
The workaround is to remember that I need to use the
abfs
protocol inobject_store
based tools such aspolars
.However, it would be nice to be able to use the
az
protocol for everything.The text was updated successfully, but these errors were encountered: