Question & suggestion

[glidester]

Is there any plan to bring the extended client in line with the standard client and produce an async version (or is this not possible due to the interactions with s3)?

It would be helpful if I could configure the client not to delete the s3 component of the message on the message delete action. This would then leave me an audit log of all the messages I'd received and I could then use the life-cycle attribute of the bucket to clear out the older messages that I no longer wish to retain.

Thanks,

Tim

[aws-aminsuzani]

Hi Tim,

Currently we are not working on an async version, but we add your feature request to our backlog for future consideration.

Thanks for the suggested option and pull request for not deleting S3 objects in DeleteMessage call. We will review the submission.

[patricksheehan]

👍 would prefer async S3 upload which triggers sending the SQS message via the handler

[rpbrehm]

Same here. I am working on a spring-cloud-aws application. Spring-cloud-aws uses the async client.

[ebezdomnikov]

Any updates?

[varunmehta]

Any updates?

@ebezdomnikov spring-attic/spring-cloud-aws#167 (comment)

[hcalsos]

Hello.
I have been using this for a while now, and i was wondering if there any plans to update the payload-offloading-java-common-lib-for-aws to support InputStreams instead of Strings when storing large files to s3.
In my use case i know the files being sent are going to be large, and would like to be able to stream the messagebody to s3 instead of having to load the entire chunk of data into memory as a string.

[richardsmithsfdc]

Here is a PR to add async to payload offloading: awslabs/payload-offloading-java-common-lib-for-aws#19 . I need reviewers, and not sure how to get anyone's attention in that repo. That support has a set of UTs along with it, and is fully consistent with the current design.

I also created a draft PR in this repo that is based on the async payload offloading change: #79 . This also has a set of UTs, and is fully consistent with the current design. It is also fully asynchronous and non-blocking.

If the payload offloading async support is approved, we can move the other PR in this repo to ready state and work on it.

Anyone who is familiar with this repo, please let me know how I can kickstart this process.