Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- breaks
-
HDFS-9301 HDFS clients can't construct HdfsConfiguration instances
- Resolved
- is depended upon by
-
HDFS-6566 Separate public and private keys in DFSConfigKey
- Open
-
HDFS-6564 Use slf4j instead of common-logging in hdfs-client
- Resolved
-
HDFS-6567 Normalize the order of public final in HdfsFileStatus
- Closed
-
HDFS-6565 Use jackson instead jetty json in hdfs-client
- Closed
- is related to
-
HADOOP-11656 Classpath isolation for downstream clients
- Resolved
- relates to
-
HADOOP-1815 Separate client and server jars
- Open
-
HDFS-9815 Move o.a.h.fs.Hdfs to hadoop-hdfs-client
- Resolved
-
HADOOP-10741 A lightweight WebHDFS client library
- Open
-
HADOOP-12499 Create a client jar for hadoop-common
- Open
-
HDFS-8048 Umbrella jira for moving HDFS client implmentation to a package
- Open