You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2018/10/12 17:53:00 UTC

[jira] [Updated] (KAFKA-7499) Extend ProductionExceptionHandler to cover serialization exceptions

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

Matthias J. Sax updated KAFKA-7499:
-----------------------------------
    Labels: beginner newbie  (was: )

> Extend ProductionExceptionHandler to cover serialization exceptions
> -------------------------------------------------------------------
>
>                 Key: KAFKA-7499
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7499
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Matthias J. Sax
>            Priority: Major
>              Labels: beginner, newbie
>
> In [KIP-210|https://cwiki.apache.org/confluence/display/KAFKA/KIP-210+-+Provide+for+custom+error+handling++when+Kafka+Streams+fails+to+produce], an exception handler for the write path was introduced. This exception handler covers exception that are raised in the producer callback.
> However, serialization happens before the data is handed to the producer with Kafka Streams itself and the producer uses `byte[]/byte[]` key-value-pair types.
> Thus, we might want to extend the ProductionExceptionHandler to cover serialization exception, too, to skip over corrupted output messages. An example could be a "String" message that contains invalid JSON and should be serialized as JSON.
> This ticket might required a KIP.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)