Based on feedback from Kirk and Colin I added configuring the parser class name via server.properties, added some tests, and updated the docs to reflect this. I find the config file name by re-parsing the command line. If anyone knows a better way of passing KafkaConfig to static initialization, I'd appreciate a nudge in the right direction. It's not the most efficient way of retrieving configs, but it is done only once at load time, so the overhead should be negligible while providing a consistent location for all configs. I have also left the system prop and env ways of passing this config in. Hopefully this is ok and is not considered a code bloat.
Thanks! Max > On Aug 29, 2024, at 10:25 AM, Maxim Fortun <m...@maxf.net> wrote: > > Hi all, > I would like to introduce a minor code change to allow custom produce request > parsers. > > KIP: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606528 > JIRA: https://issues.apache.org/jira/browse/KAFKA-17348 > PR: https://github.com/apache/kafka/pull/16812 > > There are many potential benefits for this feature. A custom produce request > parser would allow to intercept all incoming messages before they get into > the broker and apply broker wide logic to the messages. This could be a > trace, a filter, a transform(such as lineage), forcing required headers > across all messages, compression, signing, encryption, or any other message > manipulation before it gets into the broker. > > Please take a look. > Any and all feedback is greatly appreciated. > Thanks, > Max > > > >
