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

Andrew Wang commented on HDFS-11431:
------------------------------------

Hi Kai,

This JIRA (HDFS-11431) adds hadoop-hdfs as a dependency of hadoop-hdfs-client 
(and thus also hadoop-client). This pulls all the server JARs back in. It was 
committed as a quick fix to get 2.8.0 released.

As you noted, HDFS-11538 is intended as a better long term solution that moves 
CFPP to hadoop-hdfs-client, so it no longer needs to pull in the full 
hadoop-hdfs dependency (the server-side jar).

This also highlights a significant lack of testing of the hdfs client artifact. 
The hdfs client split didn't also split the tests, so we have essentially no 
test coverage for the client module by itself. It'd be great for HDFS-11538 to 
include hdfs client unit tests to help address this.

> hadoop-hdfs-client JAR does not include ConfiguredFailoverProxyProvider
> -----------------------------------------------------------------------
>
>                 Key: HDFS-11431
>                 URL: https://issues.apache.org/jira/browse/HDFS-11431
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: build, hdfs-client
>    Affects Versions: 2.8.0, 3.0.0-alpha3
>            Reporter: Steven Rand
>            Assignee: Steven Rand
>            Priority: Blocker
>              Labels: maven
>             Fix For: 2.8.0
>
>         Attachments: HDFS-11431-branch-2.8.0.001.patch, 
> HDFS-11431-branch-2.8.0.002.patch
>
>
> The {{hadoop-hdfs-client-2.8.0.jar}} file does include the 
> {{ConfiguredFailoverProxyProvider}} class. This breaks client applications 
> that use this class to communicate with the active NameNode in an HA 
> deployment of HDFS.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to