add 'data.stream.namespace' configuration property #742
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.
Problem
Currently, we cannot fully customize the target data stream.
More precisely, the namespace part of the data stream is necessarily the topic.
This is especially a problem, when you want that a connector consumes several topics for only one target data stream.
More simply, I want to be able to define target data stream name, regardless of the input topic name.
Solution
This PR aims to add a new configuration property named 'data.stream.namespace'.
This property aims to customize data stream "namespace" part (as its name says).
This is an optional setting, that have
${topic}
as default value ; so that, by default, it works as currently, no breaking change.By the way, user is able to define a custom namespace that contains topic name like that:
my_prefix_${topic}
Does this solution apply anywhere else?
If yes, where?
Test Strategy
Testing done:
Release Plan
I guess that you (Confluent Inc.) is responsible for release plan.
I am merging to master
It is safe to revert or rollback