Retry s3 reads on socket exceptions.

[asuresh8]

S3 will reset the conenction on their end frequently. To not lose data, data prepper should retry all socket exceptions by attempting to re-open the stream.

Description

Retries all socket exceptions

Issues Resolved

S3 socket exceptions causing records to get dropped

Check List

• New functionality includes testing.
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[engechas]

Changes look good to me.

I think we also need to bubble up any fatal exceptions from this class here to prevent deleting the SQS message on read failure

[asuresh8]

Changes look good to me.

I think we also need to bubble up any fatal exceptions from this class here to prevent deleting the SQS message on read failure

Good call. I've added a commit to bubble up that exception.

[opensearch-trigger-bot]

The backport to 2.3 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.3 2.3
# Navigate to the new working tree
cd .worktrees/backport-2.3
# Create a new branch
git switch --create backport/backport-2992-to-2.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9f78542533dd24ed21e29a12950938c0c4b23636
# Push it to GitHub
git push --set-upstream origin backport/backport-2992-to-2.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.3

Then, create a pull request where the base branch is 2.3 and the compare/head branch is backport/backport-2992-to-2.3.