[
https://issues.apache.org/jira/browse/FLINK-9155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321595#comment-17321595
]
Flink Jira Bot commented on FLINK-9155:
---------------------------------------
This issue and all of its Sub-Tasks have not been updated for 180 days. So, it
has been labeled "stale-minor". If you are still affected by this bug or are
still interested in this issue, please give an update and remove the label. In
7 days the issue will be closed automatically.
> 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
> Labels: stale-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
(v8.3.4#803005)
