To be clear I'm not saying I oppose deprecating it. I am not sure
whether I do or not. It's a major change and I want to make sure we
discuss it and understand if there's any work to do before removing it,
whether beeline supports everything CLI does, how it will impact users,
and how we want to communicate it to users, etc.
Thanks for understanding and being willing to pull this out while we
have the discussion.
Alan.
Szehon Ho <mailto:sze...@cloudera.com>
April 17, 2015 at 3:26
OK its fine with me. The original intent was to give recommend to users to
start thinking about migration to Beeline, as we are seeing more issues
with HiveCLI.
Thanks Lefty for digging up the thread, can discuss there.
Szehon
On Thu, Apr 16, 2015 at 3:19 PM, Lefty Leverenz <leftylever...@gmail.com>
Lefty Leverenz <mailto:leftylever...@gmail.com>
April 17, 2015 at 0:19
Here's some prior discussion:
- RE: Apache Hive 1.0 ?
<http://mail-archives.apache.org/mod_mbox/hive-dev/201412.mbox/%3c619cad26be3f904894cb11c8b3edbf222c049...@gq1-am-m03-03.y.corp.yahoo.com%3e>
(Olga
L. Natkovich: "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.")
- Deprecating CLI
<http://mail-archives.apache.org/mod_mbox/hive-dev/201412.mbox/%3c5485e1be.3060...@hortonworks.com%3e>
(Alan Gates, Thejas Nair)
-- Lefty
Alan Gates <mailto:alanfga...@gmail.com>
April 16, 2015 at 22:51
I apologize for not catching this sooner, but I'd like to revert this
patch.
Something as major as deprecating a component should be discussed on
the dev list, not just put in as a patch.
Alan.
