You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org> on 2018/01/10 02:14:02 UTC
[jira] [Commented] (FLINK-6004) Allow FlinkKinesisConsumer to skip
corrupted messages
[ https://issues.apache.org/jira/browse/FLINK-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319572#comment-16319572 ]
Tzu-Li (Gordon) Tai commented on FLINK-6004:
--------------------------------------------
Since there's been quite a while since this issue was picked up, I assume that it is currently inactive. Will pick this up.
> Allow FlinkKinesisConsumer to skip corrupted messages
> -----------------------------------------------------
>
> Key: FLINK-6004
> URL: https://issues.apache.org/jira/browse/FLINK-6004
> Project: Flink
> Issue Type: Improvement
> Components: Streaming Connectors
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: ChungChe Lai
>
> It is quite clear from the fix of FLINK-3679 that in reality, users might encounter corrupted messages from Kafka / Kinesis / generally external sources when deserializing them.
> The consumers should support simply skipping those messages, by letting the deserialization schema return {{null}}, and checking {{null}} values within the consumer.
> This has been done for the Kafka consumer already. This ticket tracks the improvement for the Kinesis consumer.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)