You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2015/02/04 23:11:34 UTC

[jira] [Moved] (HIVE-9584) Hive CLI hangs while waiting for a container

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

Hitesh Shah moved TEZ-2034 to HIVE-9584:
----------------------------------------

        Key: HIVE-9584  (was: TEZ-2034)
    Project: Hive  (was: Apache Tez)

> Hive CLI hangs while waiting for a container
> --------------------------------------------
>
>                 Key: HIVE-9584
>                 URL: https://issues.apache.org/jira/browse/HIVE-9584
>             Project: Hive
>          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)