[jira] [Updated] (FLINK-6004) Allow FlinkKinesisConsumer to skip corrupted messages
[ https://issues.apache.org/jira/browse/FLINK-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tzu-Li (Gordon) Tai updated FLINK-6004: --- Fix Version/s: 1.5.0 > 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: Tzu-Li (Gordon) Tai >Priority: Major > Fix For: 1.5.0 > > > 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 (v7.6.3#76005)
[jira] [Updated] (FLINK-6004) Allow FlinkKinesisConsumer to skip corrupted messages
[ https://issues.apache.org/jira/browse/FLINK-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aljoscha Krettek updated FLINK-6004: Component/s: Streaming Connectors > 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 > > 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.3.15#6346)
[jira] [Updated] (FLINK-6004) Allow FlinkKinesisConsumer to skip corrupted messages
[ https://issues.apache.org/jira/browse/FLINK-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tzu-Li (Gordon) Tai updated FLINK-6004: --- Description: 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. was: 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. > Allow FlinkKinesisConsumer to skip corrupted messages > - > > Key: FLINK-6004 > URL: https://issues.apache.org/jira/browse/FLINK-6004 > Project: Flink > Issue Type: Improvement >Reporter: Tzu-Li (Gordon) Tai > > 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.3.15#6346)