[
https://issues.apache.org/jira/browse/TEZ-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041648#comment-14041648
]
Bikas Saha commented on TEZ-692:
--------------------------------
Jeff, thats why I commented about having different constructors. Although, IMO
having a builder for the client itself seems a bit overdone to me.
>From the use cases, we never seem to need to actually pass anything to the
>TezClient other than the Tez client config. The AM only needs tez lib uris to
>start and credentials for the staging dir. We already infer both of them. So
>it makes sense to just have TezClient(TezConfiguration) as the main API, with
>TezClient(TezConfiguration, Credentials) for any unsupported staging dir.
>TEZ-1127 is adding support for env and additional opts via config for any
>scenarios where we actually want to specify any of them. This supports the
>case that users should not have to write code and re-compile because they
>needed the application to run on different platforms (e.g. JDK differences
>requiring special flags or optimizations). Queue is effectively already
>controlled via configuration.
The only remaining item is LocalResource. Technically, the AM does not need any
local resource to start as long as they use only Tez libraries. For any
additional local resources (eq. Hive input initializer case) we could have an
API TezClient.setAdditionalAMResources() thats optional. In the non-session
case, it ends up creating a new AM with the current set of resources. In the
TezSession case, each call will re-localize except the first one, that will use
normal localization.
> Unify job submission in either TezClient or TezSession
> ------------------------------------------------------
>
> Key: TEZ-692
> URL: https://issues.apache.org/jira/browse/TEZ-692
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: TEZ-692.1.patch
>
>
> Its confusing to have 2 ways to create and submit a tez job. The developer
> has to spend time thinking about and deciding which method to use.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
