[
https://issues.apache.org/jira/browse/FLINK-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347008#comment-16347008
]
Aljoscha Krettek edited comment on FLINK-8500 at 1/31/18 3:26 PM:
------------------------------------------------------------------
Yes, now I feel stupid. 😅 You analysed it exactly right: we do get the
timestamp from Kafka but then all of the builtin timestamp extractors
({{AscendingTimestampExtractor}} and
{{BoundedOutOfOrdernessTimestampExtractor}}) don't take that into account and
overwrite it.
You can get around that by writing a completely custom
{{AssignerWithPeriodicWatermarks}} but it's not a good situation.
was (Author: aljoscha):
Yes, no I feel stupid. 😅 You analysed it exactly right: we do get the timestamp
from Kafka but then all of the builtin timestamp extractors
({{AscendingTimestampExtractor}} and
{{BoundedOutOfOrdernessTimestampExtractor}}) don't take that into account and
overwrite it.
You can get around that by writing a completely custom
{{AssignerWithPeriodicWatermarks}} but it's not a good situation.
> 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.5.0, 1.4.1
>
> 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)
