Matthias J. Sax commented on KAFKA-5157:

It is by design. It's of course something different people have different 
opinions and both approaches has advantages/disadvantages. The design aligns 
with other components like serializers/deserializers though that use the same 

> Options for handling corrupt data during deserialization
> --------------------------------------------------------
>                 Key: KAFKA-5157
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5157
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: streams
>            Reporter: Eno Thereska
>            Assignee: Eno Thereska
>            Priority: Major
>              Labels: kip, user-experience
>             Fix For: 1.0.0
> When there is a bad formatted data in the source topics, deserialization will 
> throw a runtime exception all the way to the users. And since deserialization 
> happens before it was ever processed at the beginning of the topology, today 
> there is no ways to handle such errors on the user-app level.
>  We should consider allowing users to handle such "poison pills" in a 
> customizable way.
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-161%3A+streams+deserialization+exception+handlers

This message was sent by Atlassian JIRA

Reply via email to