[
https://issues.apache.org/jira/browse/HBASE-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992073#comment-12992073
]
stack commented on HBASE-3465:
------------------------------
bq. I am not suggesting a new hadoop lib dir. I am suggesting that hbase assume
that it will use an existing hadoop lib dir from an existing hadoop install.
There is not always an existing Hadoop install. In particular if you run HBase
standalone, it comes up fine without reference to an Hadoop cluster.
Tell me more about your hbase-with-dependencies notion Ted. I don't grok it
too well.
I appreciate your bringing this up. We've been operating this way for ages but
it has never been satisfactory. Appreciate fresh POV.
> Hbase should use a HADOOP_HOME environment variable if available.
> -----------------------------------------------------------------
>
> Key: HBASE-3465
> URL: https://issues.apache.org/jira/browse/HBASE-3465
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.0
> Reporter: Ted Dunning
> Fix For: 0.90.1, 0.92.0
>
>
> I have been burned a few times lately while developing code by having the
> make sure that the hadoop jar in hbase/lib is exactly correct. In my own
> deployment, there are actually 3 jars and a native library to keep in sync
> that hbase shouldn't have to know about explicitly. A similar problem arises
> when using stock hbase with CDH3 because of the security patches changing the
> wire protocol.
> All of these problems could be avoided by not assuming that the hadoop
> library is in the local directory. Moreover, I think it might be possible to
> assemble the distribution such that the compile time hadoop dependency is in
> a cognate directory to lib and is referenced using a default value for
> HADOOP_HOME.
> Does anybody have any violent antipathies to such a change?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
