[
https://issues.apache.org/jira/browse/KAFKA-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16514825#comment-16514825
]
Guozhang Wang commented on KAFKA-6708:
--------------------------------------
The serdes only happen in the following case:
1. when sending to an external topic or repartition topic, this is covered in
SinkNode.
2. when reading from external topic, we cover deserialization errors in the
DeserializationExceptionHandler interface, customizable in config.
3. when writing into the store, which accepts only serialized bytes (note it
includes sending to the changelog topic as well if the store is logging
enabled).
So as of now only case 3) is not captured, and the serdes happens at
MeteredXXStores, calling the serde, i.e. not centralized in one class. We can
add the logic similar in SinkNode to capture ClassCastException in the serde
calls there.
3) is being covered in
Let's pick this up in
https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-7066 and
https://github.com/apache/kafka/pull/5239
> Review Exception messages with regards to Serde Useage
> ------------------------------------------------------
>
> Key: KAFKA-6708
> URL: https://issues.apache.org/jira/browse/KAFKA-6708
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Bill Bejeck
> Priority: Major
> Labels: newbie
>
> Error messages when not including Serdes required other than the provided
> default ones should have error messages that are more specific with what
> needs to be done and possible causes than just a {{ClassCastException}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
