[
https://issues.apache.org/jira/browse/HADOOP-19654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18021168#comment-18021168
]
ASF GitHub Bot commented on HADOOP-19654:
-----------------------------------------
steveloughran commented on PR #7882:
URL: https://github.com/apache/hadoop/pull/7882#issuecomment-3307416441
ok, so maybe for s3express stores we don't do legacy MD5 plugin stuff all is
good?
1. Does imply the far end is breaking the connection when it is unhappy -at
least our unit tests found this stuff before the cost of every HEAD doubles.
2. maybe we should make the choice of checksums an enum with md5 the
default, so it is something that can be turned off/changed in future.
While on the topic of S3 Express, is it now the case that because there's
lifecycle rules for cleanup, LIST calls don't return prefixes of paths with
incomplete uploads? If so I will need to change production code and the test
-with a separate JIRA for that for completeness
> Upgrade AWS SDK to 2.33.x
> -------------------------
>
> Key: HADOOP-19654
> URL: https://issues.apache.org/jira/browse/HADOOP-19654
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build, fs/s3
> Affects Versions: 3.5.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
>
> Upgrade to a recent version of 2.33.x or later while off the critical path of
> things.
> HADOOP-19485 froze the sdk at a version which worked with third party stores.
> Apparently the new version works; early tests show that Bulk Delete calls
> with third party stores complain about lack of md5 headers, so some tuning is
> clearly going to be needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
