[
https://issues.apache.org/jira/browse/HDFS-11431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925842#comment-15925842
]
Steve Loughran commented on HDFS-11431:
---------------------------------------
One thing to consider here is that a key goal of the split of client/server was
to keep all the server classpath stuff out the client.
Could we get away with declaring hadoop-hdfs as a dependency of hadoop-client,
*but excluding the transitive dependencies which aren't needed*?
If someone does want everything, they can explicitly declare a dependency on
hadoop-hdfs, but if they ask for hadoop-client on its own, they don't get
netty, zookeeper, curator, etc, etc.
I think that'd be a good compromise.
On that topic, Allen, could we have yetus do a before/after diff on
dependencies on any patch which touches a POM? That we can always see what the
transitive effects of a dependency change are.
This is the (bash) alias I use to generate text outputs for diffing locally
{code}
alias mvndep="mvn -T 1C dependency:tree -Dverbose"
{code}
> 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
> Attachments: HDFS-11431-branch-2.8.0.001.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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
