DBZ-8752 New property rabbitmq.routingKey.source for static, topic an… #161
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
|
Hi @victorcastanogutierrez could you open a PR in the main repository with changes to the documentation about the new configuration changes? |
|
Sure thing, will do it as soon as I can |
|
@victorcastanogutierrez Applied, thanks! |
|
Thank you! |
|
Docs PR debezium/debezium#6219 |
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.
…d key states
Related issue: https://issues.redhat.com/browse/DBZ-8752
This PR adds support for a new property on the RabbitMQ sink
debezium.sink.rabbitmq.routingKey.source. The motivation is to allow not only producing to desired exchange based on the outbox table, but also being able to dynamically select the routing key from the same table.For that, this new property has the following possible values:
static(default): which will obtain the routing key fromdebezium.sink.rabbitmq.routingKeytopic: uses the value of the destination exchange as the routing keykey: uses the record key as the routing keydebezium.sink.rabbitmq.routingKeyFromTopicNameis now deprecated asdebezium.sink.rabbitmq.routingKey.sourcewithtopicvalue does the same thing. If set to true, a warn will be emitted and the value ofdebezium.sink.rabbitmq.routingKey.sourcewill becometopicin order to provide backwards compatibility