Changing the subject to reflect where the conversation is going.
It's possible to run beeline with HS2 embedded, so there's no need to
setup HS2. We could change the CLI in Hive to call beeline in this
embedded mode, thus eliminating a code path for us to test. But before
we do this there's a fair amount of compatibility work, since right now
beeline seems to give different error and status messages and exit codes
than the CLI.
Alan.
Olga L. Natkovich <mailto:ol...@yahoo-inc.com.INVALID>
December 8, 2014 at 9:08
We at Yahoo are very much against removing/deprecating CLI. This is
the most common way for our users to access Hive and we do not see
that changing any time soon. Switching everybody to HiveServer2 has
performance and scale consequences that might not be acceptable for
every use case.
I would ask to decouple Hive 1.0 discussion from removing CLI.
Thanks,
Olga
-----Original Message-----
From: Thejas Nair [mailto:the...@hortonworks.com]
Sent: Saturday, December 06, 2014 12:59 PM
To: dev@hive.apache.org
Subject: Re: Apache Hive 1.0 ?
I don't know for sure if beeline has finally reached feature parity
with hive cli. I haven't looked at that very closely. I think we
should start a separate thread on it and discuss with the community.
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or
entity to which it is addressed and may contain information that is
confidential, privileged and exempt from disclosure under applicable
law. If the reader of this message is not the intended recipient, you
are hereby notified that any printing, copying, dissemination,
distribution, disclosure or forwarding of this communication is
strictly prohibited. If you have received this communication in error,
please contact the sender immediately and delete it from your system.
Thank You.
Thejas Nair <mailto:the...@hortonworks.com>
December 6, 2014 at 12:58
I don't know for sure if beeline has finally reached feature parity
with hive cli. I haven't looked at that very closely. I think we
should start a separate thread on it and discuss with the community.
Carl Steinbach <mailto:cwsteinb...@gmail.com>
December 6, 2014 at 0:28
Hi Thejas,
I agree that it's important to give users adequate time to migrate off of
HiveCLI. In order to avoid wasting time what do you think about including
this deprecation notice in the 1.0 release?
Thejas Nair <mailto:the...@hortonworks.com>
December 4, 2014 at 15:15
HiveServer, and the original JDBC driver have already been purged in
trunk. The HiveServer1 docs have been asking users to use HiveServer2
for a long time.
The case with Hive CLI is different. We never marked that as
deprecated or asked users to use beeline instead. Beeline had been
lacking in some features until recently. We just added some
capabilities to beeline such has progress/log information support. We
need to discuss deprecating that, deprecate it and wait for some time
(at least a year or so considering how widely it is used), before we
can remove it. I think that is more like a candidate for a 2.0 .
Thanks,
Thejas
Carl Steinbach <mailto:cwsteinb...@gmail.com>
December 3, 2014 at 15:43
I'd like to see HiveCLI, HiveServer, and the original JDBC driver
deprecated and purged from the codebase before the 1.0 release. This topic
probably needs its own thread, but I thought I should mention it here.
Thanks.
- Carl
--
Sent with Postbox <http://www.getpostbox.com>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
