[
https://issues.apache.org/jira/browse/HADOOP-9385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597533#comment-13597533
]
Luke Lu commented on HADOOP-9385:
---------------------------------
+1 for moving all existing external fs client support to separate jars. IMO,
"hadoop-fs-extra" probably conveys the purpose of the project better: it's for
external/extra fs support
Though I share the maintainability concerns, there is substantial end-user
benefit of keeping the hadoop client code for these fs together. We can put a
README in the project with standard disclaimers...
> create hadoop-common-project/hadoop-filesystem-clients subprojects for
> blobstore & other clients
> ------------------------------------------------------------------------------------------------
>
> Key: HADOOP-9385
> URL: https://issues.apache.org/jira/browse/HADOOP-9385
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Affects Versions: 3.0.0
> Reporter: Steve Loughran
>
> As discussed on hadoop-general, we need somewhere to host the non-HDFS
> filesystem clients. S3/S3N, ftp are all in hadoop-common, with the JAR
> dependencies there. This doesn't scale to openstack, azure, or handle changes
> in the S3 dependencies.
> With a project of {{hadoop-common/hadoop-filesystem-clients}}, we could add
> separate FS clients: {{hadoop-filesystem-client-aws}},
> {{hadoop-filesystem-client-openstack}}, etc, each with their own tests, JARs
> and POM file dependencies. This would translate into separate bigtop
> RPMs/JARs
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
