[
https://issues.apache.org/jira/browse/KAFKA-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damian Guy resolved KAFKA-5157.
-------------------------------
Resolution: Fixed
Issue resolved by pull request 3423
[https://github.com/apache/kafka/pull/3423]
> 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
> Labels: user-experience
> Fix For: 0.11.1.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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
