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

Yi Liu commented on HDFS-6200:
------------------------------

It's great to have separate jar for hdfs-client.
I have following comments:

*1.* For long term, should we create a project {{hadoop-hdfs-common}}, and move 
the common parts which are used by hdfs client and server into that project, 
such as protocol, security token related definitions? It's a bit odd to put 
those in {{hadoop-hdfs-client}}

*2.* Currently I see we move WebHdfsFileSystem and few others into the 
{{hadoop-hdfs-client}}, I think moving the DFSClient and DistributedFileSystem 
into {{hadoop-hdfs-client}} is also in the plan?

*3.* I think moving the native hdfs client into this project is also in the 
plan?

*4.* Our target of having separate jar for hdfs-client is reducing the jar 
dependency, as [~tucu00] said, it can reduce these jars only required by hdfs 
server, not sure how many they are after we move all client related into the 
project.  If there are few, it seems not big sense we do this work. Actually I 
think we can indeed reduce many, and I need to verify it.

> Create a separate jar for hdfs-client
> -------------------------------------
>
>                 Key: HDFS-6200
>                 URL: https://issues.apache.org/jira/browse/HDFS-6200
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: build
>            Reporter: Haohui Mai
>            Assignee: Haohui Mai
>         Attachments: HDFS-6200.000.patch, HDFS-6200.001.patch, 
> HDFS-6200.002.patch, HDFS-6200.003.patch, HDFS-6200.004.patch, 
> HDFS-6200.005.patch, HDFS-6200.006.patch, HDFS-6200.007.patch
>
>
> Currently the hadoop-hdfs jar contain both the hdfs server and the hdfs 
> client. As discussed in the hdfs-dev mailing list 
> (http://mail-archives.apache.org/mod_mbox/hadoop-hdfs-dev/201404.mbox/browser),
>  downstream projects are forced to bring in additional dependency in order to 
> access hdfs. The additional dependency sometimes can be difficult to manage 
> for projects like Apache Falcon and Apache Oozie.
> This jira proposes to create a new project, hadoop-hdfs-cliient, which 
> contains the client side of the hdfs code. Downstream projects can use this 
> jar instead of the hadoop-hdfs to avoid unnecessary dependency.
> Note that it does not break the compatibility of downstream projects. This is 
> because old downstream projects implicitly depend on hadoop-hdfs-client 
> through the hadoop-hdfs jar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to