[jira] [Commented] (KAFKA-4570) How to transfer extended fields in producing or consuming requests.

["Ewen Cheslack-Postava (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15786713#comment-15786713 ] 

Ewen Cheslack-Postava commented on KAFKA-4570:
----------------------------------------------

[~zander] You're correct that Kafka does not handle extra user metadata today. However, there is an ongoing discussion to [add headers to Kafka messages|https://cwiki.apache.org/confluence/display/KAFKA/KIP-82+-+Add+Record+Headers].

> How to transfer extended fields in producing or consuming requests.
> -------------------------------------------------------------------
>
>                 Key: KAFKA-4570
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4570
>             Project: Kafka
>          Issue Type: Wish
>          Components: clients
>    Affects Versions: 0.10.1.1
>            Reporter: zander
>            Priority: Critical
>              Labels: features
>
> We encounter a problem that  we can not transfer extended fields for producing or consuming requests to the broker.
> We want to validate  the producers or consumers in a custom way other than using SSL.
> In general, such as JMS, it is possible to transfer user-related fields to server.
> But it seems that Kafka dose not support this, its protocol is very tight and  unable to add user-defined fields.
> So is there any way  achieving this goal ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)