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

Haohui Mai commented on HDFS-6200:
----------------------------------

{quote}
DFSConfigKeys should be public and contain those keys clients are expected to 
use
this is a good time to switch to SLF4J for the logging here, and drop 
commons-logging
HdfsFileStatus gets its "public final" declarations in the wrong order ... 
again, this is a good time to fix it.
JsonUtilClient uses org.mortbay.util.ajax.JSON to parse the json. Thus should 
be replaced by Jackson, so we don't need the mortbay libs on the classpath?
WebHdfsFileSystem also uses mortbay JSON for parsing
{quote}

It might be better to restrict this patch to moving the files only. I plan to 
address them in separate jiras. Filed HDFS-6564, HDFS-6565, HDFS-6566, and 
HDFS-6567 to track them.

> 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
>            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
>
>
> 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.2#6252)

Reply via email to