[
https://issues.apache.org/jira/browse/HADOOP-9385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597176#comment-13597176
]
Steve Loughran commented on HADOOP-9385:
----------------------------------------
Once a dir is chosen we can create the toplevel POM, then add the HADOOP-8545
Swift client, and then move S3/S3n support when adopting the new S3 client
library - HADOOP-9384 -
Each client should also include the new filesystem tests of HADOOP-9361,
skipping them all if the blobstore credentials aren't supplied in its
test/resources/config.xml file
> 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
