[
https://issues.apache.org/jira/browse/HADOOP-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597993#comment-16597993
]
Sean Mackrory commented on HADOOP-15694:
----------------------------------------
Attaching a patch that's basically what I want to do. Feedback welcome, but I'm
not entirely finished with this so I'm not proposing it for inclusion yet.
Integration tests are running now, but so far so good. I also still need to add
my own tests and do my own code review for silly mistakes, but I was able to
connect to ABFS by just specifying "fs.azure.account.key" without any account
context (although that'll be more useful with ABFS), and that's basically what
I wanted to achieve.
> 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.001.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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
