[
https://issues.apache.org/jira/browse/HADOOP-19627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18010894#comment-18010894
]
ASF GitHub Bot commented on HADOOP-19627:
-----------------------------------------
ahmarsuhail opened a new pull request, #7840:
URL: https://github.com/apache/hadoop/pull/7840
### Description of PR
Backport of https://github.com/apache/hadoop/pull/7816
### How was this patch tested?
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> S3A: testIfMatchOverwriteWithOutdatedEtag() fails when not using SSE-KMS
> ------------------------------------------------------------------------
>
> Key: HADOOP-19627
> URL: https://issues.apache.org/jira/browse/HADOOP-19627
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.5.0, 3.4.2
> Reporter: Ahmar Suhail
> Assignee: Ahmar Suhail
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.5.0
>
>
> ITestS3APutIfMatchAndIfNoneMatch.testIfMatchOverwriteWithOutdatedEtag() fails
> when no encryption method is set.
>
> This is because it does
> createFileWithFlags(fs, path, SMALL_FILE_BYTES, true, null);
>
> and then to overwrite the file, also does
>
> createFileWithFlags(fs, path, SMALL_FILE_BYTES, true, null);
>
> When no encryption is used, the eTAG is the md5 of the object, and so will
> always be the same, and won't result in the 412 conditional write failure.
>
> Test passes when using SSE-KMS, as when using encryption, eTag is no longer
> the md5 of the object content, and changes on every write.
>
>
> Fix is simple enough, change the object content on the second write.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
