[
https://issues.apache.org/jira/browse/KAFKA-6864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066804#comment-17066804
]
Vladimir L commented on KAFKA-6864:
-----------------------------------
Is there any reason not to make this change? I see the PR has been open for 2
years.
> null is not passed to keyDeserialzer and valueDeserializer in Fetcher
> ---------------------------------------------------------------------
>
> Key: KAFKA-6864
> URL: https://issues.apache.org/jira/browse/KAFKA-6864
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Affects Versions: 1.1.0
> Reporter: Mathias Kub
> Priority: Major
>
> Hi,
> currently null values are not passed to the keyDeserializer and
> valueDeserializer in the Fetcher class. This prevents custom deserialization
> of null values.
> The Deserializer JavaDoc says
> {code:java}
> /**
> * Deserialize a record value from a byte array into a value or object.
> * @param topic topic associated with the data
> * @param data serialized bytes; may be null; implementations are recommended
> to handle null by returning a value or null rather than throwing an exception.
> * @return deserialized typed data; may be null
> */
> T deserialize(String topic, byte[] data);{code}
> so as for my understanding, null values should be passed to it.
>
> Thanks,
> Mathias
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
