implements feature #67 to have fallback topic name support #68
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
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.
for very simple pass-through kinds of streaming ETL pipelines from kafka to mongodb it is now possible to fallback to the name of the kafka topic which is taken as is to name the corresponding mongodb collection.
the behaviour is applied iff the "default" collection name is set to an empty string in the configuration
mongodb.collection=whenever the sink connector doesn't find an explicit mapping for a kafka topic it then just uses the kafka topic name instead to fallback to the otherwise configured default mongodb collection name.
solves #67