[
https://issues.apache.org/jira/browse/HADOOP-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-11687:
-----------------------------
Attachment: HADOOP-11687.003.patch
Updated patch
* Added null checks during clone on fields that are nullable, as they appear to
cause a problem later during the CopyObject operation if a null gets through
* Fixed the findbugs suggestion
* Unrelated but added a note about core-site.xml for testing
{code}
Running org.apache.hadoop.fs.contract.s3a.TestS3AContractRename
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 130.767 sec -
in org.apache.hadoop.fs.contract.s3a.TestS3AContractRename
{code}
> 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
> Attachments: HADOOP-11687.001.patch, HADOOP-11687.002.patch,
> HADOOP-11687.003.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)
