Hi, Thanks for the KIP. A few comments. AS1: I think the work here is to create a new implementation of o.a.k.common.MessageFormatter which understands protobuf. The --formatter option on kafka-console-consumer.sh works with any class on the classpath which implements this interface.
AS2: You should also mention kafka-console-share-consumer.sh, which will be zero code change for you if the kafka-console-consumer.sh works. AS3: Please be explicit about the properties that your formatter will support. AS4: In your example commands, the --formatter-property flag is better because --property is deprecated. Thanks, Andrew On 2026/05/12 14:41:25 Sruthi Sathyamoorthy wrote: > Following up on the KIP discussion thread. > > I’d like to drive this toward a decision over the next few days. In > particular, feedback on the proposed changes would be helpful. > > If there are no blocking concerns by , I’ll proceed with the current > proposal and start implementation planning. > > > KIP: https://cwiki.apache.org/confluence/x/EZImGQ > > Thanks, > Sruthi > > On Sun, May 10, 2026 at 10:12 PM Sruthi Sathyamoorthy <[email protected]> > wrote: > > > Hello all, > > > > This email starts the discussion thread for *KIP-1337: Add Protobuf > > MessageFormatter for Kafka Console Consumer*. > > > > The proposal aims to improve the local debugging and observability > > experience for Kafka users working with protobuf-serialized messages > > without Schema Registry integration. Currently, protobuf payloads consumed > > through kafka-console-consumer.sh are not human-readable, often requiring > > custom deserialization scripts during development and troubleshooting. > > > > This KIP proposes adding a new ProtobufMessageFormatter implementation to > > Kafka’s existing formatter framework, enabling protobuf decoding using > > locally provided .proto definitions through the console consumer. > > KIP: https://cwiki.apache.org/confluence/x/EZImGQ > > Thanks, Sruthi > > >
