Alex, Both Beeline and Hive CLI are part of Hive. Your concern of either the Beeline business value or JDBC completeness doesn't seem directly related to the discussion here. Hive CLI is a legacy tool which had two main use cases: 1. a thick client for SQL on hadoop, and 2. a command line tool for HiveServer1. HiveServer1 is already deprecated and removed from Hive code base, so #2 use case is gone. For #1, Beeline provides or is supposed to provides equal functionality. There is minor syntactic difference between Beeline and Hive CLI, but there might be some gaps, which need to be identify and fixed so that we can deprecate Hive CLI.
The implementation of either Hive CLI or Beeline should not be a factor on whether we maintain either or both of them. The point here is that Hive community would like to maintain beeline and do whatever it takes to help Hive user migrate. Thanks, Xuefu On Thu, Apr 23, 2015 at 3:50 PM, Alexander Pivovarov <apivova...@gmail.com> wrote: > Hive CLI should be part of Hive project > > Beeline is a jdbc client. It should be separated from Hive (as any other > jdbc clients). > > I'm not sure I understand business value of beeline. > > Power users (which has ssh access to cluster) can use Hive CLI. > - more reliable approach because it does not need HS2 > - simpler authentication (in many cases application users do not have LDAP > password) > > Business users (LDAP users) will probably use GUI jdbc clients (e.g. SQL > Workbench/J or SQuirreL SQL) > > Is beeline production ready? > - beeline q tests were disabled about 2 years ago > > I do not think beeline is popular. > > I'd rather focus on improving JDBC driver to make sure SQL Workbench/J or > SQuirreL SQL can work with hiveserver2 effectively. > 7 months ago did several fixes for hive JDBC driver to make basic > operations work in SQL Workbench/J and SQuirreL SQL. > But lots of jdbc methods still not supported by hive jdbc driver > > > > > > > > On Thu, Apr 23, 2015 at 2:43 PM, Xuefu Zhang <xzh...@cloudera.com> wrote: > > > Hi all, > > > > I'd like to revive the discussion about the fate of Hive CLI, as this > topic > > has haunted us several times including [1][2]. It looks to me that there > is > > a consensus that it's not wise for Hive community to keep both Hive CLI > as > > it is as well as Beeline + HS2. However, I don't believe that no action > is > > the best action for us. From discussion so far, I see the following > > proposals: > > > > 1. Deprecating Hive CLI and advise that users use Beeline. > > 2. Make Hive CLI as naming flavor to beeline with embedded mode. > > > > Frankly, I don't see much difference between the two approaches. Keeping > an > > alias at script or even code level isn't that much work. However, > shouldn't > > we pick a direction and start moving to it? If there is any gaps between > > beeline embedded and Hive CLI, we should identify and fill in those. > > > > I'd love to hear the thoughts from the community and hope this time we > will > > have concrete action items to work on. > > > > Thanks, > > Xuefu > > > > [1] > > > > > http://mail-archives.apache.org/mod_mbox/hive-dev/201412.mbox/%3C5485E1BE.3060709%40hortonworks.com%3E > > [2] https://www.mail-archive.com/dev@hive.apache.org/msg112378.html > > >
