hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Da Zhou (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HADOOP-15694) ABFS: Allow OAuth credentials to not be tied to accounts
Date Wed, 12 Sep 2018 18:22:00 GMT

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

Da Zhou edited comment on HADOOP-15694 at 9/12/18 6:21 PM:
-----------------------------------------------------------

+1 from my side, the changes doesn't affect the interface which looks good to me, and the
new tests addressed the feedback above.
I'm running mvn tests locally, just in case if any thing is broken... Will update the test
results later.


was (Author: danielzhou):
+1 from my side, the changes doesn't affect the interface which looks good to me, and the
new tests addressed the feedback above.
I'm running mvn tests locally, just in case if any thing is broken... 

> ABFS: Allow OAuth credentials to not be tied to accounts
> --------------------------------------------------------
>
>                 Key: HADOOP-15694
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15694
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>            Priority: Major
>         Attachments: HADOOP-15694-HADOOP-15407-005.patch, HADOOP-15694-HADOOP-15407.003.patch,
HADOOP-15694-HADOOP-15407.004.patch, HADOOP-15694-HADOOP-15407.006.patch, HADOOP-15694-HADOOP-15407.007.patch,
HADOOP-15694.001.patch, HADOOP-15694.002.patch, HADOOP-15694.003.patch
>
>
> Now that there's OAuth support, it's possible to have a notion of identity that's distinct
from the account itself. If a cluster is configured via OAuth with it's own identity, it's
likely operators will want to use that identity regardless of which storage account a job
uses.
> So OAuth configs right now (and probably others) are looked up with <config_key>.<account>.
I propose that we add a function for looking up these configs that returns an account-specific
value if it exists, but in the event it does not will also try to return <config_key>,
if that exists.
> I can work on a patch for this if nobody has any objections.



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

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


Mime
View raw message