Description of changes
If client is configured with ignorePayloadNotFound set to true, delete SQS messages that contain pointers to S3 objects that no longer exist on S3.
Currently, AmazonSQSExtendedClient can still be configured with ignorePayloadNotFound, however this configuration option is never used which results in unexpected behaviour.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
The goal of this PR is to bring back the fix for issue https://github.com/awslabs/amazon-sqs-java-extended-client-lib/issues/30.
Description of changes If client is configured with
ignorePayloadNotFoundset totrue, delete SQS messages that contain pointers to S3 objects that no longer exist on S3.Context
ignorePayloadNotFound, however this configuration option is never used which results in unexpected behaviour.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.