Ability to provide a separate Message name for each topic when using ProtobufFile #849
Labels
type/enhancement
En enhancement to an already existing feature
Milestone
Is your proposal related to a problem?
When using a protobufFile definition for parsing messages, it is assumed that all topics use a single message type. But this assumption is not valid in a lot of common scenarios IMO. It could be helpful to use a separate message type for each topic in a cluster.
Describe the solution you'd like
Instead of setting a single message name in
protobufMessageName
when configuring a cluster, use a map oftopic -> messageName
in order to have different message names for each topic. Also, we can use a predefined key in this map (e.g._default
) to set a message name for all other topics without explicit mapping.Describe alternatives you've considered
Using Schema Registry is a better alternative when possible but in legacy deployments when messages in Kafka topics don't adhere to the format schema registry expects, this is not an option.
Additional context
I've already started working to prepare a PR, but I'd like to discuss the best solution before submitting the PR.
The text was updated successfully, but these errors were encountered: