[ 
https://issues.apache.org/jira/browse/HADOOP-19766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053955#comment-18053955
 ] 

ASF GitHub Bot commented on HADOOP-19766:
-----------------------------------------

anujmodi2021 commented on code in PR #8205:
URL: https://github.com/apache/hadoop/pull/8205#discussion_r2721667025


##########
hadoop-tools/hadoop-azure/src/site/markdown/fns_blob.md:
##########
@@ -31,8 +31,11 @@ Azure Services offers two set of endpoints for interacting 
with storage accounts
 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.
+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.
+FNS over DFS endpoint is **DEPRECATED**. All requests will be switched to Blob 
endpoint internally if

Review Comment:
   Instead of deprecated, we should say removed





> ABFS: Endpoint Conversion to Blob for FNS Accounts
> --------------------------------------------------
>
>                 Key: HADOOP-19766
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19766
>             Project: Hadoop Common
>          Issue Type: Task
>          Components: fs/azure
>    Affects Versions: 3.4.1, 3.4.2
>            Reporter: Manika Joshi
>            Assignee: Manika Joshi
>            Priority: Major
>              Labels: pull-request-available
>
> We have observed cases of ABFS driver being initialised with DFS for FNS 
> accounts which is not a recommended endpoint by the service.  
> To prevent this, we’re normalizing endpoint to Blob for FNS accounts even if 
> they were initialized with DFS endpoint.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to