[ https://issues.apache.org/jira/browse/FLINK-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461955#comment-16461955 ]
Tzu-Li (Gordon) Tai commented on FLINK-8500: -------------------------------------------- Let's go with the second approach. I've quickly checked Kafka 1.x, it seems like the \{{ConsumerRecord}} class will remain stable, at least for the near future. [~FredTing] yes, for example the Kinesis deserialization schema could benefit from a more generic solution. And yes, lets discuss them elsewhere / have a separate Jira for them. > Get the timestamp of the Kafka message from kafka consumer(Kafka010Fetcher) > --------------------------------------------------------------------------- > > Key: FLINK-8500 > URL: https://issues.apache.org/jira/browse/FLINK-8500 > Project: Flink > Issue Type: Improvement > Components: Kafka Connector > Affects Versions: 1.4.0 > Reporter: yanxiaobin > Priority: Major > Fix For: 1.6.0 > > Attachments: image-2018-01-30-14-58-58-167.png, > image-2018-01-31-10-48-59-633.png > > > The method deserialize of KeyedDeserializationSchema needs a parameter > 'kafka message timestamp' (from ConsumerRecord) .In some business scenarios, > this is useful! > -- This message was sent by Atlassian JIRA (v7.6.3#76005)