hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-13324) s3a tests don't authenticate with S3 frankfurt (or other V4 auth only endpoints)
Date Tue, 16 Aug 2016 23:40:20 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-13324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Chris Nauroth updated HADOOP-13324:
    Hadoop Flags: Reviewed

Steve, thank you for your testing against multiple S3 endpoints and documenting your findings.
 +1 for the patch.  I plan to commit this shortly after I apply one trivial fix for a typo
in index.md:

This happens when trying to work with any S3 service which only supports the
"V4" signing API —and he client is configured to use the default S3A service

"...and the client..."

> s3a tests don't authenticate with S3 frankfurt (or other V4 auth only endpoints)
> --------------------------------------------------------------------------------
>                 Key: HADOOP-13324
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13324
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 2.8.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: HADOOP-13324-branch-2-001.patch, HADOOP-13324-branch-2-001.patch
> S3A doesn't auth with S3 frankfurt. This installation only supports v4 API.
> There are some JVM options which should set this, but even they don't appear to be enough.
It appears that we have to allow the s3a client to change the endpoint with which it authenticates
from a generic "AWS S3" to a frankfurt-specific one.

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