[
https://issues.apache.org/jira/browse/TEZ-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041872#comment-14041872
]
Siddharth Seth commented on TEZ-692:
------------------------------------
bq. Will rename to getSessionStatus to getExecutionStatus
ExecutionStatus, ClientStatus - RUNNING will be the default for non-sessions.
In session status READY would apply. ClientStatus may be more meaningful w.r.t
READY.
bq. It is used by YARNRunner.
Yes, which is private to the Tez code base. We should be able to work around
this via some additional classes, and at least limit the scope to package
access. Will file a separate jira once this one is finalized and committed.
bq. Could rename to ExecutionConfiguration in this jira.
We need to handle the case of allowing per vertex configuration of parameters
like heartbeat interval, memory management, threadpool sizes, etc. I think
it'll require a separate jira anyway.
bq. Should we have additional constructors to programmatically create a session
client instead of specifying that via the configuration file?
I think that'll be useful.
bq. Having this special API seems out of band?
bq. But the user could submit another DAG. So we cannot close yarnClient.
Was looking at this with the perspective of running one dag per Tez client, but
that isn't very usable at all.
Unifying the usage, and allowing users to just flip a switch seems far more
complicated though, if at all possible, considering that a single TezClient
could use different configuration for each DAG AM, while the AM configuration
(Except for local resources) is static for a TezSession - and a TezSession does
not span Applications.
> 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)
