Hi Claus, Thanks for the quick clarification! Good to know it's a documentation labeling issue rather than a functional bug. I'll track the fix via CAMEL-23927 <https://issues.apache.org/jira/browse/CAMEL-23927>.
Thanks & Regards, Niranjan Kondru. On Mon, Jul 6, 2026 at 3:27 PM Claus Ibsen <[email protected]> wrote: > Hi > > t's expected that the consumer picks it up (the Kafka client supports it), > but the Camel documentation incorrectly shows it as producer-only. > This is a labeling bug — the fix would be changing the annotation from > "producer" to "common". > https://issues.apache.org/jira/browse/CAMEL-23927 > > On Fri, Jul 3, 2026 at 5:39 PM Niranjan Kondru <[email protected]> > wrote: > > > Hello Team, Greetings! > > > > I raised the Stack Overflow question below a couple of weeks ago and > > would like to get some insights from the Camel team. The issue is that > > a Camel Kafka consumer appears to be picking up the producer-only > > metadata.max.age.ms option. Could someone please help clarify whether > > this is expected behavior or a bug? > > > > > > > https://stackoverflow.com/questions/79962826/apache-camel-kafka-consumer-using-the-producer-only-metadatamaxagems-option-t > > > > Thanks & Regards, > > Niranjan Kondru. > > > > > -- > Claus Ibsen >
