Allow using non-default thread pool for `AsyncResponseTransformer.toFile`

[mpdn]

Describe the feature

The AsyncResponseTransformer created via toFile always uses the default thread pool in AsynchronousChannelGroup. Instead, it should be possible to give an ExecutorService as an argument to select a specific thread pool.

Use Case

I already have a thread pool dedicated to blocking IO and would like to use that one. I also generally want tight control over the threads my application is using and avoid global mutable state.

Proposed Solution

• Add an ExecutorService parameter to FileTransformerConfiguration
• In FileAsyncResponseTransformer.java, use the AsynchronousFileChannel.open variant that accepts an ExecutorService instead and supply one if configured.

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

AWS Java SDK version used

2.20.29

JDK version used

openjdk version "11.0.9" 2020-10-20 LTS

Operating System and version

MacOS Ventura 13.2.1

[debora-ito]

Feature request acknowledged. PRs are welcome :)

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.