You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2013/01/21 19:32:13 UTC
[jira] [Updated] (HBASE-7637) hbase-hadoop1-compat conflicts with
-Dhadoop.profile=2.0
[ https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated HBASE-7637:
--------------------------
Fix Version/s: 0.96.0
> hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
> --------------------------------------------------------
>
> Key: HBASE-7637
> URL: https://issues.apache.org/jira/browse/HBASE-7637
> Project: HBase
> Issue Type: Bug
> Components: build
> Affects Versions: 0.96.0
> Reporter: nkeywal
> Priority: Critical
> Fix For: 0.96.0
>
>
> I'm unclear on the root cause / fix. Here is the scenario:
> {noformat}
> mvn clean package install -Dhadoop.profile=2.0 -DskipTests
> bin/start-hbase.sh
> {noformat}
> fails with
> {noformat}
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.metrics2.lib.MetricMutable
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> {noformat}
> doing
> {noformat}
> rm -rf hbase-hadoop1-compat/target/
> {noformat}
> makes it work.
> In the pom.xml, we never reference hadoop2-compat. But doing so does not help: hadoop1-compat is compiled and takes precedence over hadoop2...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira