hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ryan rawson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3465) Hbase should use a HADOOP_HOME environment variable if available.
Date Wed, 09 Feb 2011 00:20:57 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992248#comment-12992248
] 

ryan rawson commented on HBASE-3465:
------------------------------------

we should consider using jarjar:

http://code.google.com/p/jarjar/

That way we would not have conflicting jar issues with our classpath.


> 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

        

Mime
View raw message