hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Senia (JIRA)" <>
Subject [jira] [Commented] (HIVE-10511) Replacing the implementation of Hive CLI using Beeline
Date Mon, 13 Feb 2017 20:07:41 GMT


Greg Senia commented on HIVE-10511:

[~gopalv] out of curiosity the big issue is HS2 has always been a scalability issue. So the
next question how do you plan on stopping folks on using sparkSQL cli as it goes directly
at metastore and fs which we are using along with native mr / spark going directly at the
fs system location of this data?

> Replacing the implementation of Hive CLI using Beeline
> ------------------------------------------------------
>                 Key: HIVE-10511
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 0.10.0
>            Reporter: Xuefu Zhang
>            Assignee: Ferdinand Xu
> Hive CLI is a legacy tool which had two main use cases: 
> 1. a thick client for SQL on hadoop
> 2. a command line tool for HiveServer1.
> HiveServer1 is already deprecated and removed from Hive code base, so  use case #2 is
out of the question. For #1, Beeline provides or is supposed to provides equal functionality,
yet is implemented differently from Hive CLI.
> As it has been a while that Hive community has been recommending Beeline + HS2 configuration,
ideally we should deprecating Hive CLI. Because of wide use of Hive CLI, we instead propose
replacing Hive CLI's implementation with Beeline plus embedded HS2 so that Hive community
only needs to maintain a single code path. In this way, Hive CLI is just an alias to Beeline
at either shell script level or at high code level. The goal is that  no changes or minimum
changes are expected from existing user scrip using Hive CLI.
> This is an Umbrella JIRA covering all tasks related to this initiative. Over the last
year or two, Beeline has been improved significantly to match what Hive CLI offers. Still,
there may still be some gaps or deficiency to be discovered and fixed. In the meantime, we
also want to make sure the enough tests are included and performance impact is identified
and addressed.

This message was sent by Atlassian JIRA

View raw message