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-15182) Support to change back to signature version 2 of AWS SDK
Date Fri, 19 Jan 2018 18:30:01 GMT

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

Steve Loughran commented on HADOOP-15182:


I don't want to do any form of version rollback, because it will cause too many other problems.
There's a whole history of JIRAs related to versioning things there: follow references of

Is there a way to support the V2 signer somehow? As that's what we need

> Support to change back to signature version 2 of AWS SDK
> --------------------------------------------------------
>                 Key: HADOOP-15182
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15182
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 2.9.0
>         Environment:  
>            Reporter: Yonger
>            Priority: Minor
> Current s3a depend on  aws-java-sdk-bundle-1.11.199 which use signature v4. So for
some s3-compatible system(Ceph) which still using v2, Hadoop can't work on them.
> s3cmd can use v2 via specify option like :
> {code:java}
> s3cmd --signature-v2 ls s3://xxx/{code}
> maybe we can add a parameter to allow back to use signature v2 in s3a.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message