[
https://issues.apache.org/jira/browse/TEZ-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875358#comment-13875358
]
Siddharth Seth commented on TEZ-395:
------------------------------------
bq. If we think that in the common case users will be specifying the
credentials for themselves then we can have a helper synonymous API that only
accepts credentials and uses the current process owner as the user in order to
call the full API that accepts a user and credentials.
So are you suggesting two methods on DAG 1) setCredentials(String user,
Credentials credentials) and 2) setCredentials(Credentials credentials) ?
One option is to infer the user from the UGI either when
setCredentials(Credentials) is called, or when a TezClient.submit() is called -
so if the client is trying to run as a different user, it would be submitting
the DAG under a UGI.doAs().
I'm not clear on how this will eventually be used. For this jira (Credentials
per DAG), I was thinking more in the context of multiple DAGs to the same AM,
as the same user - but potentially accessing different resources.
> Allow credentials to be specified on a per DAG basis
> ----------------------------------------------------
>
> Key: TEZ-395
> URL: https://issues.apache.org/jira/browse/TEZ-395
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Hitesh Shah
> Assignee: Michael Weng
> Attachments: TEZ-395-patch.txt
>
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
