kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5157) Options for handling corrupt data during deserialization
Date Fri, 23 Jun 2017 13:36:05 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16060908#comment-16060908
] 

ASF GitHub Bot commented on KAFKA-5157:
---------------------------------------

GitHub user enothereska opened a pull request:

    https://github.com/apache/kafka/pull/3423

    KAFKA-5157: Options for handling corrupt data during deserialization [WiP]

    This is the implementation of KIP-161: https://cwiki.apache.org/confluence/display/KAFKA/KIP-161%3A+streams+deserialization+exception+handlers

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/enothereska/kafka KAFKA-5157-deserialization-exceptions

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/3423.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3423
    
----
commit a9892b33b009385ec204bd85cdaa4a1d79e59793
Author: Eno Thereska <eno.thereska@gmail.com>
Date:   2017-06-23T13:33:22Z

    Initial implementation

----


> 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)

Mime
View raw message