You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Eric Charles (JIRA)" <ji...@apache.org> on 2012/08/16 15:48:38 UTC

[jira] [Updated] (HBASE-6581) Build with hadoop.profile=3.0

     [ https://issues.apache.org/jira/browse/HBASE-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Charles updated HBASE-6581:
--------------------------------

    Attachment: HBASE-6581-1.patch

Existing hadoop-1.0 and hadoop-2.0 profiles untouched.

Only changes on hadoop-3.0 profile.

Install and test:
mvn clean install -Dhadoop.profile=3.0 -P runSmallTests
is Successful (tests also)

hadoop-minicluster now defined with scope test, which is good.

Package:
mvn package assembly:assembly -DskipTests -Dhadoop.profile=3.0
Tests the package against hadoop 3.0 snapshot installation with simple put/get/scan via hbase shell: Success

In lib folder, only needed hadoop-*:
hadoop-annotations-3.0.0-SNAPSHOT.jar
hadoop-auth-3.0.0-SNAPSHOT.jar
hadoop-common-3.0.0-SNAPSHOT.jar
hadoop-hdfs-3.0.0-SNAPSHOT.jar
hadoop-mapreduce-client-common-3.0.0-SNAPSHOT.jar
hadoop-mapreduce-client-core-3.0.0-SNAPSHOT.jar
hadoop-yarn-api-3.0.0-SNAPSHOT.jar
hadoop-yarn-common-3.0.0-SNAPSHOT.jar
hadoop-yarn-server-common-3.0.0-SNAPSHOT.jar (not sure of this one)

Side note:
New hbase-hadoop3-compat module which imports hbase-hadoop2-compat and excludes hadoop-* jars of version 2.
Sounds not logical that hbase-hadoop3-compat relies on hbase-hadoop2-compat.
In fact, hbase-hadoop1-compat and hbase-hadoop2-compat could be renamed hbase-metrics1-compat and hbase-metrics2-compat as they are pure metrics related atm.

                
> Build with hadoop.profile=3.0
> -----------------------------
>
>                 Key: HBASE-6581
>                 URL: https://issues.apache.org/jira/browse/HBASE-6581
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Eric Charles
>         Attachments: HBASE-6581-1.patch
>
>
> Building trunk with hadoop.profile=3.0 gives exceptions (see [1]) due to change in the hadoop maven modules naming (and also usage of 3.0-SNAPSHOT instead of 3.0.0-SNAPSHOT in hbase-common).
> I can provide a patch that would move most of hadoop dependencies in their respective profiles and will define the correct hadoop deps in the 3.0 profile.
> Please tell me if that's ok to go this way.
> Thx, Eric
> [1]
> $ mvn clean install -Dhadoop.profile=3.0
> [INFO] Scanning for projects...
> [ERROR] The build could not read 3 projects -> [Help 1]
> [ERROR]   
> [ERROR]   The project org.apache.hbase:hbase-server:0.95-SNAPSHOT (/d/hbase.svn/hbase-server/pom.xml) has 3 errors
> [ERROR]     'dependencies.dependency.version' for org.apache.hadoop:hadoop-common:jar is missing. @ line 655, column 21
> [ERROR]     'dependencies.dependency.version' for org.apache.hadoop:hadoop-annotations:jar is missing. @ line 659, column 21
> [ERROR]     'dependencies.dependency.version' for org.apache.hadoop:hadoop-minicluster:jar is missing. @ line 663, column 21
> [ERROR]   
> [ERROR]   The project org.apache.hbase:hbase-common:0.95-SNAPSHOT (/d/hbase.svn/hbase-common/pom.xml) has 3 errors
> [ERROR]     'dependencies.dependency.version' for org.apache.hadoop:hadoop-common:jar is missing. @ line 170, column 21
> [ERROR]     'dependencies.dependency.version' for org.apache.hadoop:hadoop-annotations:jar is missing. @ line 174, column 21
> [ERROR]     'dependencies.dependency.version' for org.apache.hadoop:hadoop-minicluster:jar is missing. @ line 178, column 21
> [ERROR]   
> [ERROR]   The project org.apache.hbase:hbase-it:0.95-SNAPSHOT (/d/hbase.svn/hbase-it/pom.xml) has 3 errors
> [ERROR]     'dependencies.dependency.version' for org.apache.hadoop:hadoop-common:jar is missing. @ line 220, column 18
> [ERROR]     'dependencies.dependency.version' for org.apache.hadoop:hadoop-annotations:jar is missing. @ line 224, column 21
> [ERROR]     'dependencies.dependency.version' for org.apache.hadoop:hadoop-minicluster:jar is missing. @ line 228, column 21
> [ERROR] 

--
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