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

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

ahmarsuhail commented on PR #7882:
URL: https://github.com/apache/hadoop/pull/7882#issuecomment-3306500643

   @steveloughran discovered completely by accident, but it's something to do 
with the checksumming code. 
   
   If you comment out these lines: 
   
   ```
      //  builder.addPlugin(LegacyMd5Plugin.create());
   
       // do not do request checksums as this causes third-party store problems.
     //  
builder.requestChecksumCalculation(RequestChecksumCalculation.WHEN_REQUIRED);
   
       // response checksum validation. Slow, even with CRC32 checksums.
   //    if (parameters.isChecksumValidationEnabled()) {
   //      
builder.responseChecksumValidation(ResponseChecksumValidation.WHEN_SUPPORTED);
   //    }
   
   ```
   
   the test will pass. Could be something to do with s3Express not supporting 
md5, will look into it.




> 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]

Reply via email to