You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Azure Storage comes in different flavors. A "regular" Azure Storage account is a classic object store and it comes with blob endpoint (blob.core.windows.net, blob.fabric.windows.com).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
Azure Storage comes in different flavors. A "regular" Azure Storage account is a classic object store and it comes with blob endpoint (
blob.core.windows.net
,blob.fabric.windows.com
).Azure Storage Account with hierarchical namespaces enabled (aka. Azure Data Lake Gen2, Fabric OneLake) come with a second "DFS" (Distributed Filesystem) endpoint:
dfs.core.windows.net
(dfs.fabric.windows.com
) that has it's own REST-API: https://learn.microsoft.com/en-us/rest/api/storageservices/data-lake-storage-gen2This endpoint allows for potentially massive performance improvements in the following scenarios:
These are single atomic operations via DFS. With the Blob endpoint they require many individual blob operations and are therefore slower.
To my understanding, DFS-URLs are already accepted but ultimately only the blob endpoint is used by object_store.
I propose implementing the DFS endpoint in object_store and introducing a feature-flag allowing user to specify if DFS endpoint should be used.
Beta Was this translation helpful? Give feedback.
All reactions