Mailing-List: contact issues-help@tez.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tez.apache.org
Date: Wed, 4 Feb 2015 19:49:35 +0000 (UTC)
From: "Rich Haase (JIRA)" <jira@apache.org>
To: issues@tez.apache.org
Message-ID: <JIRA.12772468.1423079349000.257050.1423079375530@Atlassian.JIRA>
In-Reply-To: <JIRA.12772468.1423079349000@Atlassian.JIRA>
References: <JIRA.12772468.1423079349000@Atlassian.JIRA>
 <JIRA.12772468.1423079349285@arcas>
Subject: [jira] [Created] (TEZ-2034) Hive CLI hangs while waiting for a
 container
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Rich Haase created TEZ-2034:
-------------------------------

             Summary: Hive CLI hangs while waiting for a container
                 Key: TEZ-2034
                 URL: https://issues.apache.org/jira/browse/TEZ-2034
             Project: Apache Tez
          Issue Type: Bug
            Reporter: Rich Haase


The Hive CLI, with Tez set as the execution engine, hangs if a container cannot be immediately be allocated as the Tez application master.  From a user perspective this behavior is broken.  

Users should be able to start a CLI and execute hive metadata commands without needing a Tez application master.  Since users are accustomed to queries with Hive on MapReduce taking a long time, but access to the CLI being near instantaneous, the correct behavior should be to wait for a query to be run before starting the Tez application master.

This behavior is avoided with the Beeline CLI since it connects through HiveServer2, however many users are accustomed to using the Hive CLI and should not be penalized for their choice until the Hive CLI is completely deprecated.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)