[
https://issues.apache.org/jira/browse/HADOOP-19485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933988#comment-17933988
]
ASF GitHub Bot commented on HADOOP-19485:
-----------------------------------------
steveloughran commented on PR #7479:
URL: https://github.com/apache/hadoop/pull/7479#issuecomment-2711397748
@shameersss1 would love that s3-express stuff, and any manual testing you
can do.
The ILoad* tests against that and s3standard from within aws infra would be
good too -I'm now suspecting the SDK doesn't escalate a 503 from within a bulk
delete response into a 503 for the whole request -so nothing is retrying it.
Here's my WiP design of a new test process, and yes it is strict and time
consuming.
https://github.com/steveloughran/engineering-proposals/blob/trunk/qualifying-an-SDK-upgrade.md
I already think it's too many buckets to be realistically tested -but we do
need that mix.
Please do as much as you can. And I'll add "seek help!" to the doc -not just
to save time but to ensure even broader test setups.
> S3A: Upgrade AWS V2 SDK
> -----------------------
>
> Key: HADOOP-19485
> URL: https://issues.apache.org/jira/browse/HADOOP-19485
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: build, fs/s3
> Affects Versions: 3.4.2
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
>
> This SDK update doesn't need to come with some changes to disable some new
> features (default integrity protections),
> and to apply critical changes related to the SDK
> Default integrity protection came with 2.30, and is on unless disabled.
> https://github.com/aws/aws-sdk-java-v2/issues/5801
> As well as being incompatible with third party stores, it has also affected
> S3 multiregion Access Points:
> https://github.com/aws/aws-sdk-java-v2/issues/5878
> This has broken most interaction with third party stores, hence fixes in
> Iceberg https://github.com/apache/iceberg/pull/12264 and Trinio
> https://github.com/trinodb/trino/pull/24954
> There's also [AWS v2.30 SDK InputStream behavior changes #5859](AWS v2.30 SDK
> InputStream behavior changes).
> It looks like our code is safer from that, but it did require code review.
> SDK 2.30.19 seems good with this
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
