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/04/19 13:58:00 UTC
[jira] [Resolved] (FLINK-9204) Improve visibility of records being
skipped by the `DeserializationSchema` in the Kafka / Kinesis connectors
[ https://issues.apache.org/jira/browse/FLINK-9204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tzu-Li (Gordon) Tai resolved FLINK-9204.
----------------------------------------
Resolution: Duplicate
> Improve visibility of records being skipped by the `DeserializationSchema` in the Kafka / Kinesis connectors
> ------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-9204
> URL: https://issues.apache.org/jira/browse/FLINK-9204
> Project: Flink
> Issue Type: Improvement
> Components: Kafka Connector, Kinesis Connector, Metrics
> Reporter: Tzu-Li (Gordon) Tai
> Priority: Minor
> Fix For: 1.6.0
>
>
> Currently, users have to write some log for visibility if they are skipping some record (by returning {{null}} from the deserialization schema).
> We should have better support for this natively in the connectors, either by adding logs if {{null}} is returned by the user deserialization schema, or adding counter metrics to track how many records were skipped so far.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)