hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10373) move s3 logic to own replaceable jar, hadoop-aws
Date Thu, 27 Feb 2014 09:44:19 GMT

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

Steve Loughran commented on HADOOP-10373:
-----------------------------------------

note that this is consistent with the hadoop-openstack story, would set us up for a hadoop-azure,
etc. Having the JAR called hadoop-aws would let us add more AWS-specific features in here
(e.g. cloudfront monitors) without having to change the name

> move s3 logic to own replaceable jar, hadoop-aws
> ------------------------------------------------
>
>                 Key: HADOOP-10373
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10373
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/s3
>    Affects Versions: 2.3.0
>            Reporter: Steve Loughran
>             Fix For: 2.4.0
>
>
> After HADOOP-9565 adds a marker interface for blobstores, move s3 & s3n into their
own hadoop-amazon library
> # keeps the S3 dependencies out of the standard hadoop client dependency graph.
> # lets people switch this for alternative implementations.
> feature #2 would let you swap over to another s3n impl (e.g. amazon's) without rebuilding
everything



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message