Implement DLQ (RedrivePolicy) Functionality #37
Closed
Conversation
This file contains 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
Return attributes as part of receive_message call with optional attribute_names parameter
tiwilliam
added a commit
that referenced
this pull request
Jul 21, 2017
* dlq_functionality: Implement DLQ (RedrivePolicy) Functionality Add attributes to Message object as per SQS Message struct Return attributes as part of receive_message call with optional attribute_names parameter
|
Thanks @nritholtz! This was resolved and merged on command line, closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This will demonstrate the actual functionality of moving a message to a configured DLQ after being received the configured
Maximum Receives.This commit was made on top of #30, due to the requirement of
approximate_receive_countof theMessageto ascertain DLQ eligibility.