Skip to content

Document error behavior for SQS based events  #128

Open
@tnine

Description

@tnine

The existing examples for SQS message lamba invocations are very simple.

https://github.com/aws/aws-lambda-go/blob/master/events/README_SQS.md

It would be useful to add 2 additional examples.

Failing all messages for retry

Assuming multiple SQS messages are received, is it possible to return an error such that they are retried? I assume this is the default behavior, but it is not called out clearly in the examples.

Failing single messages/Acking individual messages

Assume 3 messages are received. The first message succeeds, the second fails, and the third succeeds. Can the lambda client use the SQS SDK in conjunction with the SQSMessage.Handle to delete messages 1, and 3 directly, causing only message 2 to be retried?

The above use cases are valid use cases in SQS queue consumption, but the documentation in lambda invocation is not clear on how to accomplish these use cases. If they could be added, it would be very helpful for new users.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions