hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mithun Radhakrishnan (JIRA)" <>
Subject [jira] [Commented] (HIVE-10304) Add deprecation message to HiveCLI
Date Thu, 16 Apr 2015 22:42:58 GMT


Mithun Radhakrishnan commented on HIVE-10304:

Hello, [~szehon]. Pardon the delay; I wish I'd responded sooner.

There was a discussion on the dev user-list that concluded that we shouldn't be deprecating
the Hive command-line until we have interface/error-code parity between beeline and the CLI.
is one thread. To quote:

bq. +1 to the idea of embedding beeline within hive cli, and retaining core behavior such
as exit codes in hive-cli while doing that... users don't have to specify parameters like
jdbc url, username etc.

The issue I see here is that there are still Hive installations that depend on the CLI, and
don't depend entirely on HS2 deploys. (Where I work, for instance.) I'd be very keen to see
the embedded-beeline option in working order.

Could we please discuss this check-in? I don't know if it's a good idea to push this into
the impending release. I fear that the deprecation will be too disruptive, without proper

> Add deprecation message to HiveCLI
> ----------------------------------
>                 Key: HIVE-10304
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: CLI
>    Affects Versions: 1.1.0
>            Reporter: Szehon Ho
>            Assignee: Szehon Ho
>              Labels: TODOC1.2
>             Fix For: 1.2.0
>         Attachments: HIVE-10304.2.patch, HIVE-10304.3.patch, HIVE-10304.patch
> As Beeline is now the recommended command line tool to Hive, we should add a message
to HiveCLI to indicate that it is deprecated and redirect them to Beeline.  
> This is not suggesting to remove HiveCLI for now, but just a helpful direction for user
to know the direction to focus attention in Beeline.

This message was sent by Atlassian JIRA

View raw message