THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Ideally, Hive CLI should be deprecated as the Hive community has long recommended using the Beeline plus HiveServer2 configuration; however, because of the wide use of Hive CLI, we instead are replacing Hive CLI's implementation with a new Hive CLI on top of Beeline plus embedded HiveServer2 (HIVE-10511) so that the Hive community only needs to maintain a single code path. In this way, the new Hive CLI is just an alias to Beeline at both the shell script level and the high code level. The goal is that no or minimal changes are required from existing user scripts using Hive CLI.
Hive CLI Functionality Support
We use a new Hive CLI on top of Beeline to implement the Hive CLI functionality. In case some existing Hive CLI features are not supported in Beelinethe new Hive CLI, we are able to use the following command to use the deprecated old Hive CLI tool.
| No Format |
|---|
export USE_DEPRECATED_CLI=true |
...
| Configuration Name | Supported in New Hive CLI |
|---|---|
| hive.cli.errors.ignore | Yes |
| hive.cli.prompt | Yes |
| hive.cli.pretty.output.num.cols | No |
| hive.cli.print.current.db | No |
...
The lower the score the better since we are evaluating the time cost. There is not a no clear performance gap in terms of retrieving data.
...