We are missing the larger issue here. Bigtop only cares about two entry points does not mean there are only two we should care about. We have hive web interface, hive-thrift-service, lineage tool. Oozie should probably interface with the Hive-thrift-service I did that here: https://github.com/edwardcapriolo/m6d_oozie/blob/master/src/main/java/com/m6d/oozie/HiveServiceBAction.java. Thrift is the best programmatic way to interface with hive.
We have a long standing ticket open to standardize the environment for all these processes so they all have a common entry point. (I can not find the ticket ATM).
We are always going to need something like HADOOP_HOME because hive assumes hadoop jars are "provided" (like in maven terms) and hadoop configuration is "provided". Unless we copy all the hadoop jars to hive/lib and copy all the hadoop configuration to hive. With the patch about we still use HADOOP_HOME to build the classpath to start hive.
Also HADOOP_HOME is deprecated but in the setup docs "http://hadoop.apache.org/common/docs/r0.23.1/hadoop-yarn/hadoop-yarn-site/SingleCluster.html"
"Assuming that the environment variables $HADOOP_COMMON_HOME, $HADOOP_HDFS_HOME, $HADOO_MAPRED_HOME, $YARN_HOME, $JAVA_HOME and $HADOOP_CONF_DIR have been set appropriately. Set $$YARN_CONF_DIR the same as $HADOOP_CONF_DIR"
I still feel like hive is going to end up using environment variables to start up.