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

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

Github user steveloughran commented on the issue:

    https://github.com/apache/hadoop/pull/339
  
    OK. For absolute strictness, and this is the same rules we apply 
everywhere: which azure endpoint (e.g ireland, US, etc). (this declaration 
forces max honesty)
    
    BTW, have a look at 
https://github.com/steveloughran/cloudstore/releases/tag/tag_2018-02-13-release-2
 and see what it does when given an ADL fs URI with this patch: it should list 
the origin of the patched properties 
https://github.com/steveloughran/cloudstore/releases/tag/tag_2018-02-13-release-2


> ADLS to support per-store configuration
> ---------------------------------------
>
>                 Key: HADOOP-13972
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13972
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/adl
>    Affects Versions: 3.0.0-alpha2
>            Reporter: John Zhuge
>            Priority: Major
>
> Useful when distcp needs to access 2 Data Lake stores with different SPIs.
> Of course, a workaround is to grant the same SPI access permission to both 
> stores, but sometimes it might not be feasible.
> One idea is to embed the store name in the configuration property names, 
> e.g., {{dfs.adls.oauth2.<store>.client.id}}. Per-store keys will be consulted 
> first, then fall back to the global keys.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to