-
-
Notifications
You must be signed in to change notification settings - Fork 350
Fixing sqs fifo message order consuming #192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
} | ||
catch (MessagingException messagingException) { | ||
applyDeletionPolicyOnError(receiptHandle); | ||
if (!applyDeletionPolicyOnError(receiptHandle)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was wondering about this also. Perhaps it would be a little clearer like this ? (Just a proposition)
if (!applyDeletionPolicyOnError(receiptHandle)) { | |
if (shouldDeleteMessageOnError(receiptHandle)) { | |
deleteMessage(receiptHandle); | |
} else { | |
break; | |
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeh, I agree with you, it would be clearer
Thanks @fernandomoraes for contribution and apologies for late review. Looks legit 👌 |
Lets consider #124 (comment) before merging. |
Ok, it's already included. |
thanks @fernandomoraes and @sebastiandusza! |
📢 Type of change
📜 Description
SQS FIFO messages aren't being consumed in a correct order. The order miss occurs when an error is throwable by the consumer handler.
💡 Motivation and Context
When message of a certain message group could not be consumed, newer messages from the same message group should wait until this message be consumed with success or the message dropped by the sqs.
💚 How did you test it?
📝 Checklist
🔮 Next steps