allow user to configure subscriber timeout for input stream #5017
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
Change is required when uploading large files via S3 (transfer manager/S# async client). Currently the sequence of events needed to perform this operation:
BlockingInputStreamAsyncRequestBody
The second step can take longer than 10 seconds (default) for larger uploads.
Modifications
Similar to #5000 for output stream, allow user to configure this subscriber timeout value for input stream as well.
Testing
Unit test to verify we can set the timeout now
Types of changes
It is only exposing the ability to set a value. If user misconfigures the value it could potentially break their software.
Change is backward compatible and does not change the functionality of any existing code
Checklist
mvn install
succeedsscripts/new-change
script and following the instructions. Commit the new file created by the script in.changes/next-release
with your changes.License