Fix issue with fifo queues message failure reporint issue#175
Merged
Conversation
…ped messages when an earlier message fails. #174
1 task
normj
force-pushed
the
normj/fix-fifo-failover
branch
from
224eb83 to
b3db809
Compare
ashishdhingra
approved these changes
Feb 17, 2025
boblodgett
approved these changes
Feb 17, 2025
normj
force-pushed
the
normj/fix-fifo-failover
branch
from
b3db809 to
70ad8d8
Compare
boblodgett
approved these changes
Feb 18, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Issue #, if available:
#174
Description of changes:
While processing messages in Lambda if we get a failure in a message group we skip processing the remaining messages. We should be reporting to Lambda as part of the SQSBatchResponse the items we skipped as failures so Lambda doesn't think they were successfully processed.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.