You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/10/31 12:55:27 UTC

[jira] [Resolved] (HADOOP-9385) create hadoop-common-project/hadoop-filesystem-clients subprojects for blobstore & other clients

     [ https://issues.apache.org/jira/browse/HADOOP-9385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran resolved HADOOP-9385.
------------------------------------
       Resolution: Won't Fix
    Fix Version/s: 3.0.0

> 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
>             Fix For: 3.0.0
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)