You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Naveen Gangam (Jira)" <ji...@apache.org> on 2020/11/02 17:44:00 UTC

[jira] [Created] (HIVE-24348) Beeline: Isolating dependencies and execution with java

Naveen Gangam created HIVE-24348:
------------------------------------

             Summary: Beeline: Isolating dependencies and execution with java
                 Key: HIVE-24348
                 URL: https://issues.apache.org/jira/browse/HIVE-24348
             Project: Hive
          Issue Type: Improvement
          Components: Beeline
    Affects Versions: 3.1.0
            Reporter: Naveen Gangam
            Assignee: Naveen Gangam


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



--
This message was sent by Atlassian Jira
(v8.3.4#803005)