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 "Denis Jannot (JIRA)" <ji...@apache.org> on 2015/03/08 11:18:38 UTC

[jira] [Created] (HADOOP-11687) Ignore x-emc-* headers when copying an Amazon S3 object

Denis Jannot created HADOOP-11687:
-------------------------------------

             Summary: Ignore x-emc-* headers when copying an Amazon S3 object
                 Key: HADOOP-11687
                 URL: https://issues.apache.org/jira/browse/HADOOP-11687
             Project: Hadoop Common
          Issue Type: Bug
          Components: fs/s3
    Affects Versions: 2.7.0
            Reporter: Denis Jannot


The EMC ViPR/ECS object storage platform uses proprietary headers starting by x-emc-* (like Amazon does with x-amz-*).
Headers starting by x-emc-* should be included in the signature computation, but it's not done by the Amazon S3 Java SDK (it's done by the EMC S3 SDK).

When s3a copy an object it copies all the headers, but when the object includes x-emc-* headers, it generates a signature mismatch.

Removing the x-emc-* headers from the copy would allow s3a to be compatible with the EMC ViPR/ECS object storage platform.

Removing the x-* which aren't x-amz-* headers from the copy would allow s3a to be compatible with any object storage platform which is using proprietary headers



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)