ABFS Driver for Namespace Disabled Accounts (FNS: Flat Namespace)

Note: FNS-BLOB Support is being built and not yet ready for usage.

Background

The ABFS driver is recommended to be used only with HNS Enabled ADLS Gen-2 accounts for big data analytics because of being more performant and scalable.

However, to enable users of legacy WASB Driver to migrate to ABFS driver without needing them to upgrade their general purpose V2 accounts (HNS-Disabled), Support for FNS accounts is being added to ABFS driver. Refer to WASB Deprication for more details.

Azure Service Endpoints Used by ABFS Driver

Azure Services offers two set of endpoints for interacting with storage accounts: 1. Azure Blob Storage referred as Blob Endpoint 2. Azure Data Lake Storage referred as DFS Endpoint

The ABFS Driver by default is designed to work with DFS Endpoint only which primarily supports HNS Enabled Accounts only.

To enable ABFS Driver to work with FNS Accounts, Support for Blob Endpoint is being added. This is because Azure services do not recommend using DFS Endpoint for FNS Accounts. ABFS Driver will only allow FNS Accounts to be accessed using Blob Endpoint. HNS Enabled accounts will still use DFS Endpoint which continues to be the recommended stack based on performance and feature capabilities.

Configuring ABFS Driver for FNS Accounts

Following configurations will be introduced to configure ABFS Driver for FNS Accounts: 1. Account Type: Must be set to false to indicate FNS Account xml <property> <name>fs.azure.account.hns.enabled</name> <value>false</value> </property>

  1. Account Url: It is the URL used to initialize the file system. It is either passed directly to file system or configured as default uri using “fs.DefaultFS” configuration. In both the cases the URL used must be the blob endpoint url of the account. 
    <property>
  <name>fs.defaultFS</name>
  <value>https://ACCOUNT_NAME.blob.core.windows.net</value>
</property>
  2. Service Type for FNS Accounts: This will allow an override to choose service type specially in cases where any local DNS resolution is set for the account and driver is unable to detect the intended endpoint from above configured URL. If this is set to blob for HNS Enabled Accounts, FS init will fail with InvalidConfiguration error. 
    

    3. 



 fs.azure.fns.account.service.type BLOB  ```


    


  1. Service Type for Ingress Operations: This will allow an override to choose service type only for Ingress Related Operations like Create, Append and Flush. All other operations will still use the configured service type.


    

    

    

    2. 



 fs.azure.fns.account.service.type BLOB  ```