Support for storage accounts in the URL (Azure Data Lake Storage Gen2 URI support) about adlfs HOT 2 OPEN

What's the actual work to be done here? IIUC, can we just need to parse that URI and extract the account URL and container name used by the existing implementation? You can use regular azure-storage-blob to work with these kinds of containers? Or do we need to use another API to talk to Azure?

If we can use azure.storage.blob, then I think we would need to

• Decide on whether to overload the existing AzureBlobFileSystem.__init__ to also accept being called with this URI type. That's probably the most convenient for users but might be a bit tricky to implement (it kinda clashes with the current implementation). Maybe it'd be best to have a separate FileSystem class that handles this URI, which internally uses AzureBlobFileSystem?
• Register abfs[s] as prefixes with fsspec
• tests

from adlfs.

It would be great to have support for abfss too!

from adlfs.