[
https://issues.apache.org/jira/browse/HBASE-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203784#comment-13203784
]
Roman Shaposhnik commented on HBASE-5221:
-----------------------------------------
Guys, this fix will break certain HADOOP 0.23 layout. The correct fix for this
one will have to come out of HBASE-5286
It would be really nice if folks can chime in on the JIRA that I quoted.
Also, I don't quite understand why this is a problem. For developer's builds
HBase bundles everything under lib and thus has no reason to look under HADOOP
installation tree. For pacakged deployments (Bigtop, CDH) the layout of Hadoop
is different anyway, which means this fix will actually break things.
> bin/hbase script doesn't look for Hadoop jars in the right place in trunk
> layout
> --------------------------------------------------------------------------------
>
> Key: HBASE-5221
> URL: https://issues.apache.org/jira/browse/HBASE-5221
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.0
> Reporter: Todd Lipcon
> Assignee: Jimmy Xiang
> Fix For: 0.94.0
>
> Attachments: hbase-5221.txt
>
>
> Running against an 0.24.0-SNAPSHOT hadoop:
> ls: cannot access
> /home/todd/ha-demo/hadoop-0.24.0-SNAPSHOT/hadoop-common*.jar: No such file or
> directory
> ls: cannot access /home/todd/ha-demo/hadoop-0.24.0-SNAPSHOT/hadoop-hdfs*.jar:
> No such file or directory
> ls: cannot access
> /home/todd/ha-demo/hadoop-0.24.0-SNAPSHOT/hadoop-mapred*.jar: No such file or
> directory
> The jars are rooted deeper in the heirarchy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
