Hello, Establishing an explicit, first-party per-record processing boundary provides a much more reliable scope for observability extensions; it allows tools to hook directly into individual record processing, rather than relying on batch iteration that can be bypassed during pre-processing, which significantly reduces the boilerplate required for instrumentation and context management.
Best Regards, Yury On 2026/04/01 15:13:55 Aditya Kousik wrote: > Hi all, > > I'd like to start a discussion on KIP-1305: Per-Record Context Processing for > Kafka Consumers. > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1305%3A+Per-Record+Context+Processing+for+Kafka+Consumers > > Spring Kafka, SmallRye, Micronaut, OTel, and Datadog have each independently > built per-record lifecycle hooks because the client doesn't provide one. This > KIP proposes ConsumerRecordContextProcessor, a configurable hook that creates > a per-record AutoCloseable context via record.newContext(), giving frameworks > and instrumentation libraries a single stable integration point. > > Looking forward to your feedback. > > Thanks, > Aditya Kousik >
