Mailing-List: contact issues-help@tez.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tez.incubator.apache.org
Date: Fri, 23 Aug 2013 22:15:51 +0000 (UTC)
From: "Hitesh Shah (JIRA)" <jira@apache.org>
To: issues@tez.incubator.apache.org
Message-ID: <JIRA.12662284.1375852557295.25812.1377296151754@arcas>
In-Reply-To: <JIRA.12662284.1375852557295@arcas>
References: <JIRA.12662284.1375852557295@arcas>
Subject: [jira] [Resolved] (TEZ-349) Add initial support for Tez Sessions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/TEZ-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hitesh Shah resolved TEZ-349.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 0.2.0

Committed to master.
                
> Add initial support for Tez Sessions
> ------------------------------------
>
>                 Key: TEZ-349
>                 URL: https://issues.apache.org/jira/browse/TEZ-349
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Siddharth Seth
>            Assignee: Hitesh Shah
>              Labels: TEZ-0.2.0
>             Fix For: 0.2.0
>
>         Attachments: TEZ-349.2.wip.patch, TEZ-349.3.patch, TEZ-349.proposal.patch
>
>
> Requested by [~hagleitn].
> Essentially, users of TezClient (Hive in this case) would create a Tez session. This session can then be used to submit multiple DAGs. 
> Internally, TezClient can control whether an AM is run within the same process, in unmanaged mode, on the cluster etc. Initially, we'd likely end up creating one AM per submitted DAG. Once TEZ-340 is in place, the same AM could be re-used for multiple non-concurrent DAGs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira