[jira] Commented: (HBASE-3465) Hbase should use a HADOOP_HOME environment variable if available.

["stack (JIRA)" <ji...@apache.org>]

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

stack commented on HBASE-3465:
------------------------------

I'm not mad about having new hadoop only lib dir.  What if hadoop were in a subdir of lib?  Then you could do your HADOOP_HOME into lib/hadoop as default and if overridden, we use the alternative.

But I'm kinda easy on this.  Currently its a bit of a pain, especially so with 0.90.0, given as we'll more than likely be deployed atop an Hadoop we are not compatible with.

> 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.
-
You can reply to this email to add a comment to the issue online.