[
https://issues.apache.org/jira/browse/KAFKA-19650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajarshi Misra reassigned KAFKA-19650:
--------------------------------------
Assignee: Rajarshi Misra
> Add message key to org.apache.kafka.clients.producer.RecordMetadata
> -------------------------------------------------------------------
>
> Key: KAFKA-19650
> URL: https://issues.apache.org/jira/browse/KAFKA-19650
> Project: Kafka
> Issue Type: Wish
> Components: clients, streams
> Reporter: Schubert Fernandes
> Assignee: Rajarshi Misra
> Priority: Minor
> Labels: needs-kip
>
> Although the message key is not really {_}metadata{_}, it may be useful to
> include it in the _org.apache.kafka.clients.producer.RecordMetadata_ class so
> that metdata can be tied back to a specific message.
> When using a standard Kafka producer it is easy to tie back the metadata to a
> specific message by using the callback mechanism.
> However, when using Kafka streams, the only way to access the metadata and
> log the details is to register a stream-level
> _org.apache.kafka.clients.producer.ProducerInterceptor_ instance.
> This mechanism has a drawback in that it is impossible to tie the
> RecordMetadata instance back to a particular message.
> Including the message key in the metadata would solve this problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
