hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9385) create hadoop-common-project/hadoop-filesystem-clients subprojects for blobstore & other clients
Date Fri, 08 Mar 2013 16:38:13 GMT

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

Alejandro Abdelnur commented on HADOOP-9385:

Along the lines of what I've just commented on the email thread,

Unless those filesystems are part of hadoop, their clients should not be distributed/build
by hadoop. My concern is testability and maintainability.

> 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

View raw message