[
https://issues.apache.org/jira/browse/TEZ-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041415#comment-14041415
]
Bikas Saha commented on TEZ-692:
--------------------------------
I was also thinking of renaming this to TezClient.
SessionNotRunning - will fix.
Will rename to getSessionStatus to getExecutionStatus - so it applies to both
session execution and non-session execution.
bq.Unrelated to this jira, but the method public DAGClient
submitDAGApplication(ApplicationId appId, DA
It is used by YARNRunner.
bq. submitDAG(DAG dag, Map<String, LocalResource> additionalAmResources)
I was thinking of allowing a setAMConfiguration() method can be used to update
the AM configuration. That also works for non-session mode. For session mode,
this could check if the update can be made eg. only resource addition would be
supported. Having this special API seems out of band?
bq. In non session mode (public DAGClient submitDAGApplication(ApplicationId
appId, DAG dag) - the yarn client can be shut down
But the user could submit another DAG. So we cannot close yarnClient.
bq. AMConfiguration.tezConf
Could rename to ExecutionConfiguration in this jira.
> 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)
