Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.1.0
Description
Currently, beeline code, binaries and executables are somewhat tightly coupled with the hive product. To be able to execute beeline from a node with just JRE installed and some jars in classpath is impossible.
- beeline.sh/hive scripts rely on HADOOP_HOME to be set which are designed to use "hadoop" executable to run beeline.
- Ideally, just the hive-beeline.jar and hive-jdbc-standalone jars should be enough but sadly they arent. The latter jar adds more problems than it solves because all the classfiles are shaded some dependencies cannot be resolved.
- Beeline has many other dependencies like hive-exec, hive-common. hadoop-common, supercsv, jline, commons-cli, commons-io, commons-logging etc. While it may not be possible to eliminate some of these, we should atleast have a self-contains jar that contains all these to be able to make it work.
- the underlying script used to run beeline should use JAVA as an alternate means to execute if HADOOP_HOME is not set
Attachments
Issue Links
- is related to
-
HIVE-24591 Move Beeline To SLF4J Simple Logger
- Open
- Testing discovered
-
HIVE-25750 Beeline: Creating a standalone tarball by isolating dependencies
- Closed
- links to