[
https://issues.apache.org/jira/browse/FLINK-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369081#comment-16369081
]
Aljoscha Krettek commented on FLINK-8500:
-----------------------------------------
I've moved this to 1.6 because we're already very late with the feature freeze
for 1.5. There exists a workaround of writing a custom timestamp extractor that
is not derived from {{AscendingTimestampExtractor}} or
{{BoundedOutOfOrdernessTimestampExtractor}}, there you can implement the method
{{extractTimestamp(T, long)}} which has access to the current timestamp, which
is the Kafka timestamp in case of using the Kafka source.
> 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: Blocker
> 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)
