[
https://issues.apache.org/jira/browse/HIVE-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261921#comment-13261921
]
Roman Shaposhnik commented on HIVE-2757:
----------------------------------------
@Carl, bin/hive shell script calling bin/hadoop is a bit of an orthogonal issue
here I think. The basic problem I'm trying to address in this JIRA is this:
hive has at least 2 entry points Bigtop cares about for integration purposes:
# bin/hive
# org.apache.hadoop.hive.cli.CliDriver
Regardless of which one is used, though, hive Java code will end up exec'ing
hadoop launcher script when it comes to job submission. The reason I'm brining
up the 2 is simple: given that #2 exists and is used by things like Oozie we
can't rely on shell-level computation of environment (like finding the hadoop
executable and passing that to java code via a property, etc.).
What this JIRA is trying to accomplish is to push the logic of finding hadoop
executable script (if none is given) back to the java code, since because of #2
it is the only place where it can be done reliably.
Makes sense?
> hive can't find hadoop executor scripts without HADOOP_HOME set
> ---------------------------------------------------------------
>
> Key: HIVE-2757
> URL: https://issues.apache.org/jira/browse/HIVE-2757
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
