You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (Jira)" <ji...@apache.org> on 2019/12/28 23:44:00 UTC
[jira] [Resolved] (KAFKA-9202) serde in ConsoleConsumer with access
to headers
[ https://issues.apache.org/jira/browse/KAFKA-9202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guozhang Wang resolved KAFKA-9202.
----------------------------------
Fix Version/s: 2.5.0
Reviewer: Guozhang Wang
Resolution: Fixed
> serde in ConsoleConsumer with access to headers
> -----------------------------------------------
>
> Key: KAFKA-9202
> URL: https://issues.apache.org/jira/browse/KAFKA-9202
> Project: Kafka
> Issue Type: Improvement
> Components: consumer
> Affects Versions: 2.3.0
> Reporter: Jorg Heymans
> Assignee: huxihx
> Priority: Major
> Fix For: 2.5.0
>
>
> ML thread here : [https://lists.apache.org/thread.html/ab8c3094945cb9f9312fd3614a5b4454f24756cfa1a702ef5c739c8f@%3Cusers.kafka.apache.org%3E]
>
> The Deserializer interface has two methods, one that gives access to the headers and one that does not. ConsoleConsumer.scala only calls the latter method. It would be nice if it were to call the default method that provides header access, so that custom serde that depends on headers becomes possible.
> Currently it does this:
>
> {code:java}
> deserializer.map(_.deserialize(topic, nonNullBytes).toString.
> getBytes(StandardCharsets.UTF_8)).getOrElse(nonNullBytes)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)