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

Eric Yang commented on HADOOP-16444:
------------------------------------

[~lingchao] Application developer should not depend on Hadoop transitive 
dependencies to obtain HBase jar files.  This could be very fragile when Hadoop 
needs to evolve at its own pace to use a new version of HBase for it's own 
internal service like YARN Timeline service.  The recommended approach is to 
define dependency exclusions in pom.xml for your application to prevent 
sourcing Hadoop specific version of HBase, then define HBase dependency 
separately.  This would ensure your application gets the right version of HBase 
jar file and isolated from Hadoop internal.

{code}
<dependency>
  <groupId>org.apache.hadoop</groupId>
  <artifactId>hadoop-common</artifactId>
  <version>3.2.0</version>
  <exclusions>
    <exclusion>
      <groupId>org.apache.hbase</groupId>
      <artifactId>hbase-common</artifactId>
    </exclusion>
  </exclusions>
</dependency>
{code}

> Updating incompatible issue
> ---------------------------
>
>                 Key: HADOOP-16444
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16444
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: net
>    Affects Versions: 3.1.2
>            Reporter: xia0c
>            Priority: Major
>              Labels: performance
>
> Hi,
> When I try to update hadoop-common to the latest version 3.2.0. I got an 
> incompatible issue with hbase. It works on version 2.5.0-cdh5.3.10.
> {code:java}
> public String getFoo()
> {
>       public void Test() throws Exception{
>               HBaseTestingUtility htu1 = new HBaseTestingUtility();
>               htu1.startMiniCluster();
>       }
> }
> {code}
> Thanks a lot



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to