You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/12/04 15:13:00 UTC

[jira] [Commented] (HADOOP-13972) ADLS to support per-store configuration

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

Steve Loughran commented on HADOOP-13972:
-----------------------------------------

The S3A code should be pulled up to hadoop common for this; we don't want different semantics of per4-bucket options

including the (as yet uncommitted) work on jceks support, where getPassword() looks for the bucket keys ahead of any more general ones: HADOOP-14507


> 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
>
> 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
(v6.4.14#64029)

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