hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9385) create hadoop-common-project/hadoop-filesystem-clients subprojects for blobstore & other clients
Date Fri, 30 Oct 2015 22:58:27 GMT

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

Chris Nauroth commented on HADOOP-9385:
---------------------------------------

[~stevel@apache.org], is this still an issue you'd like to keep open, or are you satisfied
with the current structure under hadoop-tools?

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

Mime
View raw message