This makes S3 rehydration go considerably faster and fixes an issue when paging through more than 1,000 objects. Unless the client has connectivity issues with SNS, there should no error checking required on the threads (the SNS service has its own message retry policy). Futures are stored in a list in case we want to make error checking an option later.
How Has This Been Tested?
Tested with a production deployment (similar to the S3/SNS example in the repo).
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Description
Motivation and Context
This makes S3 rehydration go considerably faster and fixes an issue when paging through more than 1,000 objects. Unless the client has connectivity issues with SNS, there should no error checking required on the threads (the SNS service has its own message retry policy). Futures are stored in a list in case we want to make error checking an option later.
How Has This Been Tested?
Tested with a production deployment (similar to the S3/SNS example in the repo).
Types of changes
Checklist: