hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amandeep Khurana (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10372) Deprecate S3 implementation.
Date Fri, 28 Feb 2014 06:06:20 GMT

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

Amandeep Khurana commented on HADOOP-10372:
-------------------------------------------

bq. I'm not sure about deprecation as S3 does some things that s3n doesn't.

Interesting point, [~stevel@apache.org]. I'd be curious to understand more. What are the things
that S3 does that are useful to users and that can't be done with S3N? If you think there
is functionality in S3 because of which it should be kept around, would it make sense to consider
implementing that in S3N and having a single option (if that implementation is possible)?

> Deprecate S3 implementation.
> ----------------------------
>
>                 Key: HADOOP-10372
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10372
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3
>            Reporter: Amandeep Khurana
>            Priority: Minor
>
> We encourage users to use the S3N implementation. We should consider deprecating the
older S3 implementation to avoid confusion down the road.



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

Mime
View raw message