[
https://issues.apache.org/jira/browse/HADOOP-12499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968795#comment-14968795
]
Steve Loughran commented on HADOOP-12499:
-----------------------------------------
bq. For example, hadoop-common-client should not depend on guava.
doesn't that mean cutting out all {{@visibleFortesting}} and Precondition
logic? I'm not a fan of Guava, but it does provide stuff that we need.
Have you managed to rm it from HDFS-client? What was lost in the process —and
how did you replace it?
> Create a client jar for hadoop-common
> -------------------------------------
>
> Key: HADOOP-12499
> URL: https://issues.apache.org/jira/browse/HADOOP-12499
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Haohui Mai
> Assignee: Haohui Mai
>
> HDFS-6200 has refactor the HDFS client implementations into the
> {{hadoop-hdfs-client}} module. However, the client module still depends on
> {{hadoop-common}} which contains both the implementation of hadoop server and
> clients.
> This jira proposes to separate client-side implementation of
> {{hadoop-common}} to a new module {{hadoop-common-client}} so that both the
> yarn and the hdfs client no longer need to transitively bring in dependency
> in the server side.
> Per feedbacks from [~steve_l] and [~cmccabe], the development will happen in
> a separate branch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
