You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2019/02/28 15:21:01 UTC

[jira] [Updated] (FLINK-9155) Provide message context information in DeserializationSchema

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

Robert Metzger updated FLINK-9155:
----------------------------------
    Component/s: Connectors / Kafka

> Provide message context information in DeserializationSchema
> ------------------------------------------------------------
>
>                 Key: FLINK-9155
>                 URL: https://issues.apache.org/jira/browse/FLINK-9155
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Kafka
>            Reporter: Alex Smirnov
>            Priority: Minor
>
> There's no way to retrieve more information about corrupted message in the DeserializationSchema class. It is only possible to return null, which is a signal to skip the message, and to throw an exception, which will cause job failure.
> For investigation purposes it would be good to have more information, like:
>  * kafka topic from which the message came from
>  ** in Flink 1.4, it is possible to subscribe using Pattern, so topic name is not always evident
>  * kafka topic offset
> The idea is to write this information into the log file for further analysis. Having topic name and offset allows to retrieve the message and investigate it.



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