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

use of 'az' as a shorter version of 'abfs` #373

Closed
raybellwaves opened this issue Aug 7, 2020 · 1 comment
Closed

use of 'az' as a shorter version of 'abfs` #373

raybellwaves opened this issue Aug 7, 2020 · 1 comment

Comments

@raybellwaves
Copy link
Contributor

This is more of a discussion than a features request.

Looking at known_implementations there are gcs and gs which both point to gcsfs.GCSFileSystem. Could az be created as a shorter version of abfs?

Caveats

Unlike gs and s3, Azure has two classes (adlfs.AzureDatalakeFileSystem and adlfs.AzureBlobFileSystem). I imagine you can't use az for both classes.

Proposed solution

Use az as a shortcut for 'abfs': {'class': 'adlfs.AzureBlobFileSystem'}. Given this is for the latest version of storage (Azure Datalake Gen2 and Azure Blob Storage). In addition my 50 % reduction in key strokes motivation doesn't apply to adl (Azure Datalake Gen1).

If you prefer me to open at https://github.com/dask/adlfs I will do so.

@martindurant
Copy link
Member

az is common with Azure CLI syntax

This is a good enough reason for me; but yes, please ask on the adlfs repo, to poll for preferences.

Note that at some point I really want to implement an entrypoints method for packages to declare the fsspec drivers they contain, so that the protocol string is listed in one place only. However that wouldn't solve the case where a protocol driver is not installed and the user could do with a nice message telling them whet to do about it.

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