You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2016/07/20 20:11:20 UTC

[jira] [Updated] (KAFKA-3977) KafkaConsumer swallows exceptions raised from message deserializers

     [ https://issues.apache.org/jira/browse/KAFKA-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gustafson updated KAFKA-3977:
-----------------------------------
    Priority: Blocker  (was: Critical)

> KafkaConsumer swallows exceptions raised from message deserializers
> -------------------------------------------------------------------
>
>                 Key: KAFKA-3977
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3977
>             Project: Kafka
>          Issue Type: Bug
>          Components: consumer
>    Affects Versions: 0.9.0.0, 0.9.0.1, 0.10.0.0
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Blocker
>             Fix For: 0.10.0.1
>
>
> Message deserialization is currently done in the FetchResponse handler which is executed by NetworkClient. Unfortunately, this means that any exceptions raised by the deserializer will be eaten by NetworkClient and not raised to users. This will be fixed (if unintentionally) in KAFKA-3888, but we should make sure that this is fixed in 0.9.0 and 0.10.0 as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)