[
https://issues.apache.org/jira/browse/HADOOP-19258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879018#comment-17879018
]
ASF GitHub Bot commented on HADOOP-19258:
-----------------------------------------
steveloughran commented on PR #7015:
URL: https://github.com/apache/hadoop/pull/7015#issuecomment-2327388439
regarding the others
* ITestS3AConcurrentOps. hit that in #6938 where I'd assumed it was my
change that did it: maybe it just guaranteed it would also surface.
* ITestS3AConfiguration looks like its due to a private field change. If you
can see what it was changed to we could migrate the test case -if not, it'll
need cutting.
Other ones I'm unsure about -could be race conditions based on where you
are, or its library changes. Assume for now that they're test regressions as
some assumptions are invalid, rather than library regressions. (I think you can
see why we like to isolate SDK updates from everything else...)
Can you just do a checkout of trunk with no changes, run the same tests and
see what the results are?
> Update AWS Java SDK to 2.27.14
> -------------------------------
>
> Key: HADOOP-19258
> URL: https://issues.apache.org/jira/browse/HADOOP-19258
> Project: Hadoop Common
> Issue Type: Task
> Components: build, fs/s3
> Reporter: Diljot Grewal
> Priority: Major
> Labels: pull-request-available
>
> Upgrade SDK to add IfNoneMatch support for upcoming PutIfNotExist
> functionality
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
