[
https://issues.apache.org/jira/browse/HADOOP-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221453#comment-15221453
]
Hudson commented on HADOOP-11687:
---------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9541 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9541/])
HADOOP-11687. Ignore x-* and response headers when copying an Amazon S3 (harsh:
rev 256c82fe2981748cd0befc5490d8118d139908f9)
*
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AFileSystem.java
* hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/index.md
> Ignore x-* and response headers when copying an Amazon S3 object
> ----------------------------------------------------------------
>
> Key: HADOOP-11687
> URL: https://issues.apache.org/jira/browse/HADOOP-11687
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/s3
> Affects Versions: 2.7.0
> Reporter: Denis Jannot
> Assignee: Harsh J
> Fix For: 2.9.0
>
> Attachments: HADOOP-11687.001.patch, HADOOP-11687.002.patch,
> HADOOP-11687.003.patch, HADOOP-11687.004.patch
>
>
> 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)
