[
https://issues.apache.org/jira/browse/HBASE-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068978#comment-13068978
]
Alejandro Abdelnur commented on HBASE-3465:
-------------------------------------------
Thanks Stack.
On 1st comment: Does Hbase require Hadoop tests JARs? If so we should not only
include it. But the problem we'll have there is its transitive dependencies
(which are not in the Hadoop's lib).
On 2nd comment: left are right are not the same, *build* and *lib*. BTW, this
is in the original script, it shows modified (the - is before all the +).
> 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
> Assignee: Alejandro Abdelnur
> Attachments: a1-HBASE-3465.patch
>
>
> 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
