Adding Debezium #1
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
Also adding Connect container and example connector configuration
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.
Hey @kbastani, as discussed here's a PR for adding Debezium to the demo. This currently captures all the tables from the orderweb application, whereas eventually, it should only capture the outbox table.
Are you going to change the application so that it writes the events into such table, instead of directly writing to Kafka? If so, I then could update the Debezium configuration, so to read from that outbox table exclusively. Ideally, the outbox table would have a schema as described here. Then the outbox routing SMT in Debezium could pretty much be used as-is. No problem if not though (if you prefer other column names for instance), just let me know and I can configure things as needed.