[
https://issues.apache.org/jira/browse/HADOOP-19627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18010882#comment-18010882
]
ASF GitHub Bot commented on HADOOP-19627:
-----------------------------------------
hadoop-yetus commented on PR #7839:
URL: https://github.com/apache/hadoop/pull/7839#issuecomment-3135670118
:broken_heart: **-1 overall**
| Vote | Subsystem | Runtime | Logfile | Comment |
|:----:|----------:|--------:|:--------:|:-------:|
| +0 :ok: | reexec | 7m 10s | | Docker mode activated. |
| -1 :x: | patch | 0m 7s | |
https://github.com/apache/hadoop/pull/7839 does not apply to branch-3.4. Rebase
required? Wrong Branch? See
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute for help.
|
| Subsystem | Report/Notes |
|----------:|:-------------|
| Docker | ClientAPI=1.51 ServerAPI=1.51 base:
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7839/1/artifact/out/Dockerfile
|
| GITHUB PR | https://github.com/apache/hadoop/pull/7839 |
| Console output |
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7839/1/console |
| versions | git=2.25.1 |
| Powered by | Apache Yetus 0.14.0 https://yetus.apache.org |
This message was automatically generated.
> 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
