[
https://issues.apache.org/jira/browse/HDFS-11431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924995#comment-15924995
]
Steven Rand commented on HDFS-11431:
------------------------------------
I tried the naive approach of simply moving {{ConfiguredFailoverProxyProvider}}
into {{hadoop-hdfs-client}}, but that gets messy quickly due to the other
classes in {{hadoop-hdfs}} that it imports, and the classes that they import,
etc. I imagine that approach can be made to work, but not without a substantial
refactor.
Maybe the best thing to do is to make {{hadoop-client}} depend on
{{hadoop-hdfs}} as suggested by [[email protected]] and others in HDFS-9301?
> 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
> Priority: Blocker
> Labels: maven
>
> 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]
