You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2009/09/05 01:20:59 UTC
[jira] Resolved: (HBASE-1817) Add to package documentation the need
of zk to be in classpath
[ https://issues.apache.org/jira/browse/HBASE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-1817.
--------------------------
Resolution: Invalid
Assignee: stack
We already have doc. in the o.a.h.h.mapreduce package documentation that says explicitly that you should add zk to CLASSPATH:
{code}
<p>MapReduce jobs deployed to a MapReduce cluster do not by default have access
to the HBase configuration under <code>$HBASE_CONF_DIR</code> nor to HBase classes.
You could add <code>hbase-site.xml</code> to $HADOOP_HOME/conf and add
hbase jars to the <code>$HADOOP_HOME/lib</code> and copy these
changes across your cluster but a cleaner means of adding hbase configuration
and classes to the cluster <code>CLASSPATH</code> is by uncommenting
<code>HADOOP_CLASSPATH</code> in <code>$HADOOP_HOME/conf/hadoop-env.sh</code>
adding hbase dependencies here. For example, here is how you would amend
<code>hadoop-env.sh</code> adding the
built hbase jar, zookeeper (needed by hbase client), hbase conf, and the
<code>PerformanceEvaluation</code> class from the built hbase test jar to the
hadoop <code>CLASSPATH<code>:
....
{code}
Resolving as invalid.
> Add to package documentation the need of zk to be in classpath
> --------------------------------------------------------------
>
> Key: HBASE-1817
> URL: https://issues.apache.org/jira/browse/HBASE-1817
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Fix For: 0.20.1
>
>
> Add to package documentation the need of zk to be in classpath as of 0.20.0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.