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

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

manika137 commented on code in PR #8152:
URL: https://github.com/apache/hadoop/pull/8152#discussion_r2665012927


##########
hadoop-tools/hadoop-azure/src/site/markdown/index.md:
##########
@@ -838,6 +837,58 @@ requests. User can specify them as fixed SAS Token to be 
used across all the req
         </property>
         ```
 
+    - ABFS allows you to implement your custom SAS Token Provider. The 
declared class must implement

Review Comment:
   No. We had earlier mentioned to add configs for both OAuth and delegated SAS 
by referring to the sections above. For SAS however, the configs remain 
constant since we dont have multiple implementations of it (unlike OAuth).
   Would be better to mention all fixed configs ones at one place so user only 
needs to check configs for OAuth implementation





> 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