hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Buddhika Chamith De Alwis (JIRA)" <>
Subject [jira] [Commented] (HIVE-2757) hive can't find hadoop executor scripts without HADOOP_HOME set
Date Tue, 01 May 2012 17:00:48 GMT


Buddhika Chamith De Alwis commented on HIVE-2757:

Recently I had this requirement of getting hive running in local mode without the assumption
of HADOOP_HOME being set. My use case was to run Hive embedded inside an OSGi environment
running the Hive Thrift Service. So I had to make some changes in local mode job submission
codes to directly invoke Hadoop instead of going through Hadoop scripts. I am attaching the
changes as a patch in case you folks find it useful. I took the liberty of defining couple
of new properties so that it would continue to work with Hadoop scripts as normal if above
properties are not explicitly set. Anyway this doesn't take away the HADOOP_HOME requirement
to start hive using hive scripts since they are heavily dependent on being HADOOP_HOME set.
In my case this was sufficient since I was starting Hive server programatically without going
through hive scripts. Also here I have used a HADOOPLIB property where I assume all Hadoop
related dependencies are present. In my case this was not bound to HADOOP_HOME, was just a
specific location inside OSGi container where all Hive and Hadoop jars were present together.
> hive can't find hadoop executor scripts without HADOOP_HOME set
> ---------------------------------------------------------------
>                 Key: HIVE-2757
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 0.8.0
>            Reporter: Roman Shaposhnik
>         Attachments: HIVE-2757.patch.txt
> The trouble is that in Hadoop 0.23 HADOOP_HOME has been deprecated. I think it would
be really nice if bin/hive can be modified to capture the which hadoop
> and pass that as a property into the JVM.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message