[ 
https://issues.apache.org/jira/browse/HADOOP-19654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18035983#comment-18035983
 ] 

ASF GitHub Bot commented on HADOOP-19654:
-----------------------------------------

steveloughran opened a new pull request, #8059:
URL: https://github.com/apache/hadoop/pull/8059

   
   AWS SDK upgraded to 2.35.4.
   
   This SDK has changed checksum/checksum headers handling significantly, 
causing problems with third party stores, and, in some combinations AWS S3 
itself.
   
   The S3A connector has retained old behavior; options to change these 
settings are now available.
   
   The default settings are chosen for maximum compatiblity and performance.
   
   fs.s3a.request.md5.header:       true
   fs.s3a.checksum.generation:      false
   fs.s3a.create.checksum.algorithm: ""
   
   Consult the documentation for more details.
   
   Contributed by Steve Loughran
   
   
   ### How was this patch tested?
   
   in progress. 
   
   ### For code changes:
   
   - [X] 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)?
   - [X] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   




> Upgrade AWS SDK to 2.35.4
> -------------------------
>
>                 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]

Reply via email to