Prevent validating crc32 checksum on incomplete response stream

[L-Applin]

This change is to enhance customer experience when dealing with IOException. It will prevent validating checksum when an error is encountered during reading the response body input stream and return to the user the actual error that cause a read to fail instead of the erroneous Crc32MismatchException.

Motivation and Context

When an error is encountered during reading the response body, the un-marshalling of the json response is aborted. The un-marshalling abortion logic includes a call to InputStream.close() which in turns will trigger validating the checksum (checksum validation is performed upon closing the Crc32ChecksumValidatingInputStream). Currently, this checksum validation will then throw a Crc32MismatchException since only part of the body was read. The error returned to the user will be this Crc32MismatchException and the underlying actual cause for the failure to read from the input stream will be ignored and difficult to troubleshoot.

Modifications

Add a flag to Crc32ChecksumValidatingInputStream class to not validate checksum if an error is encounter during reading from the response input stream.

Testing

Added unit test.
Manual test against dynamodb.

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

[sonarcloud]

Quality Gate failed

Failed conditions
D Reliability Rating on New Code (required ≥ A)
B Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint