Add test for the application of message-ttl policy retroactively #1425
Conversation
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
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.
Tests the behavior of the queues when a
message-ttlpolicy is applied retroactively.At the moment, if there are messages in the queue when the policy is applied, these messages aren't drained after the
ttl. However, the documentation (https://www.rabbitmq.com/ttl.html#per-message-ttl-caveats) states that they are drained when they reach the head of the queue, and aren't delivered to consumers.Expire those messages is complex, as the timestamp when they entered the queue is missing. Current behaviour could be accepted, and only a documentation update required.