You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "YangHai (Jira)" <ji...@apache.org> on 2023/06/05 07:18:00 UTC
[jira] [Resolved] (NIFI-11136) FetchS3Object Client calculated content hash didn't match hash calculated by Amazon S3
[ https://issues.apache.org/jira/browse/NIFI-11136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
YangHai resolved NIFI-11136.
----------------------------
Resolution: Not A Problem
Just add "-Dcom.amazonaws.services.s3.disableGetObjectMD5Validation=true" to the jvm startup parameter
> FetchS3Object Client calculated content hash didn't match hash calculated by Amazon S3
> --------------------------------------------------------------------------------------
>
> Key: NIFI-11136
> URL: https://issues.apache.org/jira/browse/NIFI-11136
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.19.1
> Reporter: YangHai
> Priority: Major
> Attachments: image-2023-02-03-17-50-01-199.png
>
>
> I created three processer, as shown in the picture below, an error occurred when the first processer ListS3 listed the file name and passed it to the fetchS3Object to get the data:
> Caused by: com.amazonaws.SdkClientException: Unable to verify integrity of data download. Client calculated content hash didn't match hash calculated by Amazon S3. The data may be corrupt.
>
> !image-2023-02-03-17-50-01-199.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)