Add blog post AMQP 1.0 Modified Outcome #2095
Merged
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
Deploying rabbitmq-website with
|
| Latest commit: |
b4ceb51
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://464bb958.rabbitmq-website.pages.dev |
| Branch Preview URL: | https://modified-outcome.rabbitmq-website.pages.dev |
ansd
added a commit
to rabbitmq/rabbitmq-server
that referenced
this pull request
Oct 11, 2024
as described in rabbitmq/rabbitmq-website#2095 This commit adds a test case and fixes a bug in the broker to allow using `array` type in the value of the modified annotations.
ansd
added a commit
to rabbitmq/rabbitmq-server
that referenced
this pull request
Oct 11, 2024
Support tracking the requeue history as described in rabbitmq/rabbitmq-website#2095 This commit: 1. adds a test case tracing the requeue history via AMQP 1.0 using the modified outcome and 2. fixes bugs in the broker which crashed if a modified message annotation value is an AMQP 1.0 list, map, or array. Modified annotations are stored as tagged values from now on. These modified annotations can be consumed via AMQP 1.0, but not via AMQP 0.9.1, which is okay.
ansd
added a commit
to rabbitmq/rabbitmq-server
that referenced
this pull request
Oct 11, 2024
Support tracking the requeue history as described in rabbitmq/rabbitmq-website#2095 This commit: 1. adds a test case tracing the requeue history via AMQP 1.0 using the modified outcome and 2. fixes bugs in the broker which crashed if a modified message annotation value is an AMQP 1.0 list, map, or array. Modified annotations are stored as tagged values from now on. These modified annotations can be consumed via AMQP 1.0, but not via AMQP 0.9.1, which is okay.
which is easier to repro for the blog post reader
ansd
added a commit
to rabbitmq/rabbitmq-server
that referenced
this pull request
Oct 11, 2024
Support tracking the requeue history as described in rabbitmq/rabbitmq-website#2095 This commit: 1. adds a test case tracing the requeue history via AMQP 1.0 using the modified outcome and 2. fixes bugs in the broker which crashed if a modified message annotation value is an AMQP 1.0 list, map, or array. Modified annotations are stored as tagged values from now on. These modified annotations can be consumed via AMQP 1.0, but not via AMQP 0.9.1, which is okay.
ansd
added a commit
to rabbitmq/rabbitmq-server
that referenced
this pull request
Oct 11, 2024
Test the use case described in rabbitmq/rabbitmq-website#2095
ansd
added a commit
to rabbitmq/rabbitmq-server
that referenced
this pull request
Oct 11, 2024
Support tracking the requeue history as described in rabbitmq/rabbitmq-website#2095 This commit: 1. adds a test case tracing the requeue history via AMQP 1.0 using the modified outcome and 2. fixes bugs in the broker which crashed if a modified message annotation value is an AMQP 1.0 list, map, or array. Complex modified annotation values (list, map, array) are stored as tagged values from now on. This means AMQP 0.9.1 consumers will not receive modified annotations of type list, map, or array (which is okay).
ansd
added a commit
to rabbitmq/rabbitmq-server
that referenced
this pull request
Oct 11, 2024
Test the use case described in rabbitmq/rabbitmq-website#2095
ansd
added a commit
to rabbitmq/rabbitmq-server
that referenced
this pull request
Oct 11, 2024
Test the use case described in rabbitmq/rabbitmq-website#2095: > Rather than relying solely on RabbitMQ's built-in dead lettering tracking via x-opt-deaths, consumers can customise dead lettering event tracking.
mergify bot
pushed a commit
to rabbitmq/rabbitmq-server
that referenced
this pull request
Oct 11, 2024
Support tracking the requeue history as described in rabbitmq/rabbitmq-website#2095 This commit: 1. adds a test case tracing the requeue history via AMQP 1.0 using the modified outcome and 2. fixes bugs in the broker which crashed if a modified message annotation value is an AMQP 1.0 list, map, or array. Complex modified annotation values (list, map, array) are stored as tagged values from now on. This means AMQP 0.9.1 consumers will not receive modified annotations of type list, map, or array (which is okay). (cherry picked from commit e6818f0)
mergify bot
pushed a commit
to rabbitmq/rabbitmq-server
that referenced
this pull request
Oct 11, 2024
Test the use case described in rabbitmq/rabbitmq-website#2095 (cherry picked from commit 855a32a)
mergify bot
pushed a commit
to rabbitmq/rabbitmq-server
that referenced
this pull request
Oct 11, 2024
Test the use case described in rabbitmq/rabbitmq-website#2095: > Rather than relying solely on RabbitMQ's built-in dead lettering tracking via x-opt-deaths, consumers can customise dead lettering event tracking. (cherry picked from commit 2e90619)
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.
No description provided.