You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2018/01/18 23:37:00 UTC
[jira] [Commented] (HADOOP-15182) Support to change back to
signature version 2 of AWS SDK
[ https://issues.apache.org/jira/browse/HADOOP-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331424#comment-16331424 ]
Steve Loughran commented on HADOOP-15182:
-----------------------------------------
There is a switch for that already, isn’t there?
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org