[
https://issues.apache.org/jira/browse/HIVE-9584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358899#comment-14358899
]
Hari Sekhon commented on HIVE-9584:
-----------------------------------
I've noticed this problem today too.
I suggest container start be done in another thread in the background and the
CLI be presented to the user for metadata operations without requiring a tez
container.
> 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)
