hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13972) ADLS to support per-store configuration
Date Thu, 15 Feb 2018 12:38:00 GMT

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

ASF GitHub Bot commented on HADOOP-13972:

Github user steveloughran commented on the issue:

    2-3 hours, normally. It can get a bit confused about PRs, which is why I've stopped doing
it, even though github review is nice. 
    if nothing happens, create a new JIRA, same title + "Yetus patch checker", mark as a duplicate
of the original, and do a `git diff trunk...HEAD > HADOOP-13972-001.patch` call to build
that first patch, attach it to the JIRA and submit. here's [an example](https://issues.apache.org/jira/browse/HADOOP-15003)

> 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
>            Assignee: Sharad Sonker
>            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

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

View raw message