[
https://issues.apache.org/jira/browse/BIGTOP-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709984#comment-13709984
]
Nick Dimiduk commented on BIGTOP-955:
-------------------------------------
Funny you should ask :)
I have a wider goal of making it transparent for users to consume HBase from
\{Pig,Hive,HCat\}, at least as far as establishing classpath and dependency
jars are concerned. They shouldn't need to know about HBase-specific classpath
entries or dependencies shipped with their MR job. I want it to be as "easy" to
use HBase as it is to use HDFS in this regard. If the distro (BigTop) can
provide well-known "hooks," ie these environment variables, then the launch
scripts can detect of the presence of HBase and inspect it for additional
necessary details. There's more work to be done for both the launch scripts and
the dependency shipping, but this is an important component.
See also HIVE-2055, HIVE-2379, HCATALOG-621, PIG-2786, PIG-3285, HBASE-8438.
Some of these will need readdressed for proper Windows support as well.
> HBase installation should advertise its location and configuration
> ------------------------------------------------------------------
>
> Key: BIGTOP-955
> URL: https://issues.apache.org/jira/browse/BIGTOP-955
> Project: Bigtop
> Issue Type: Improvement
> Affects Versions: 0.5.0
> Reporter: Nick Dimiduk
> Assignee: Sean Mackrory
> Attachments: 0001-BIGTOP-955-advertise-hbase.patch
>
>
> Integration between HBase and other data tools can be improved. Work on
> HIVE-2055, PIG-2786 and HCATALOG-621 will allow those tools' launch scripts
> (project-local {{bin/XXX}}) to include HBase jars and configuration on the
> classpath when {{HBASE_HOME}} and {{HBASE_CONF_DIR}} are defined. I believe
> it is BigTop's responsibility to provide that environment for HBase
> deployments, similar to how {{HADOOP_HOME}} is provided.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
