[
https://issues.apache.org/jira/browse/KAFKA-20320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066286#comment-18066286
]
Andrew Schofield commented on KAFKA-20320:
------------------------------------------
[~ssathy10] It is probably worth discussing how this is intended to work. I can
think of a few ways:
* Adding a new Kafka CLI tool, which will definitely require a small KIP
* Create a kind of formatter that can be used with
bin/kafka-console-consumer.sh which understands protobuf, that might perhaps
need a small KIP. You need to implement
org.apache.kafka.common.MessageFormatter and there are several formatters
already in existence.
Personally, I'm not sure this merits an entirely new tool so I suggest you see
if you can get the second of these to work, and then create a KIP.
> Build Kafka CLI tool to decode Protobuf messages using local proto definitions
> ------------------------------------------------------------------------------
>
> Key: KAFKA-20320
> URL: https://issues.apache.org/jira/browse/KAFKA-20320
> Project: Kafka
> Issue Type: Improvement
> Components: tools
> Reporter: Sruthi Sathyamoorthy
> Priority: Major
>
> Build a utility that consumes Kafka messages and decodes protobuf serialized
> payloads using {{.proto}} definitions loaded from a specified directory. This
> is intended for environments where protobuf messages are not registered in a
> schema registry. The tool should dynamically resolve message types and log
> decoded fields for debugging and observability.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
