You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2014/06/21 03:39:24 UTC
[jira] [Commented] (TEZ-692) Unify job submission in either
TezClient or TezSession
[ https://issues.apache.org/jira/browse/TEZ-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039635#comment-14039635 ]
Bikas Saha commented on TEZ-692:
--------------------------------
After this patch any Tez DAG should run in session or non-session mode based on configuration.
1) Removes TezClient. TezSession is the only API and the focus of the patch is to minimally break existing users who have already written a bunch of TezSession code. Their code should mostly work as is.
2) Add new Tez configuration tez.am.shared with default true. If this is set then sessions are enabled.
3) Adds stop() to lifecycle. start() creates yarnclient. stop() closes yarnclient(). In session mode, start also starts the session AM.
4) submitDAG() goes to session in session mode or creates a new application
5) TezSession accepts an AMConfiguration only. Other duplicate and unused stuff has been removed.
Refactoring. Hence expecting existing tests to provide coverage.
The name TezSession and config name tez.am.shared have room for improvement.
[~hitesh] Please review.
> 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)