[
https://issues.apache.org/jira/browse/TEZ-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875347#comment-13875347
]
Bikas Saha commented on TEZ-395:
--------------------------------
Since credentials are in the context of a user, it makes sense for the API to
allow a user to be specified. 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.
Its not clear to me why the patch is changing AMConfiguration. If that is for
TEZ-674 then we should do it in that jira. Agree that we need to keep MR out of
tez-dag-api.
> 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)
