-
Notifications
You must be signed in to change notification settings - Fork 104
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' #78
Comments
I'm open to the idea, but I'd like to get feedback from @martindurant. When we settled on abfs as the protocol, it was based on the fact that abfs:// is the defined protocol for AzureBlobFileSystem, as described here. |
I just saw that this discussion started in fsspec. I'm OK with it. As a side-note, I've also started to see the "az://" show up in at least one other place as well. |
You can, of course, have both protocols. |
Yeah I was thinking of making it akin to I'm thinking of seeing the following in
|
OK, so go ahead! |
@raybellwaves -- I'm good with this. Are you planning to submit a PR? |
Closed via #111 |
Moved from filesystem_spec to here
This is more of a discussion than a feature request.
Looking at
known_implementations
in fsspec there aregcs
andgs
which both point togcsfs.GCSFileSystem
. Couldaz
be created as a shorter version ofabfs
?az is common with Azure CLI syntax e.g. docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-v10#run-azcopy.
As someone who is very lazy I prefer two key strokes instead of four.
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).The text was updated successfully, but these errors were encountered: