We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
I would like to ask whether it is possible that when message is publish and consider duplicated it will be route to dead letter exchange and queue?
desired behavior
x-deduplication-header
"1"
The text was updated successfully, but these errors were encountered:
I am unsure whether it is possible. I will have a look at RMQ source code to see if this can be easily supported.
Sorry, something went wrong.
issue #106: support new RMQ rabbit_backing_queue:is_duplicate syntax
bdedc84
Signed-off-by: Matteo Cafasso <[email protected]>
issue #106: add dead-letter exchange support tests
f5b368c
Since 0.7.0 and RMQ v4.1.0, duplicate messages will go to the configured deadletter queue.
0.7.0
v4.1.0
No branches or pull requests
I would like to ask whether it is possible that when message is publish and consider duplicated it will be route to dead letter exchange and queue?
desired behavior
x-deduplication-header
:"1"
already in queuex-deduplication-header
:"1"
The text was updated successfully, but these errors were encountered: