You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (JIRA)" <ji...@apache.org> on 2019/02/22 11:24:00 UTC

[jira] [Closed] (FLINK-8354) Add KafkaDeserializationSchema that directly uses ConsumerRecord

     [ https://issues.apache.org/jira/browse/FLINK-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aljoscha Krettek closed FLINK-8354.
-----------------------------------
       Resolution: Implemented
    Fix Version/s: 1.8.0
     Release Note: For the Flink KafkaConsumers, we introduced a new KafkaDeserializationSchema that gives direct access to the Kafka ConsumerRecord. This subsumes the KeyedSerializationSchema functionality, which is deprecated but still available for now.

Added on master in
9e6495175aba30ef3be27a5ff0e5f59ec5c42f72

> Add KafkaDeserializationSchema that directly uses ConsumerRecord
> ----------------------------------------------------------------
>
>                 Key: FLINK-8354
>                 URL: https://issues.apache.org/jira/browse/FLINK-8354
>             Project: Flink
>          Issue Type: New Feature
>          Components: Kafka Connector
>         Environment: Kafka 0.11.0.0
> Flink 1.4.0
> flink-connector-kafka-0.11_2.11 
>            Reporter: Mohammad Abareghi
>            Assignee: Aegeaner
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.8.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> This allows using all fields that Kafka offers on {{ConsumerRecord}}, for example, timestamps and headers.
> h2. Old Text
> Kafka has introduced notion of Header for messages in version 0.11.0.0  https://issues.apache.org/jira/browse/KAFKA-4208.
> But flink-connector-kafka-0.11_2.11 which supports kafka 0.11.0.0 ignores headers when consuming kafka messages. 
> It would be useful in some scenarios, such as distributed log tracing, to support message headers to FlinkKafkaConsumer011 and FlinkKafkaProducer011. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)