[
https://issues.apache.org/jira/browse/FLINK-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462143#comment-16462143
]
ASF GitHub Bot commented on FLINK-8500:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/5939
The feature is a nice addition.
Flink currently already adds the timestamp as the record's event time
timestamp. You can access it via a ProcessFunction. That is a tad bit more
clumsy, though...
If we want to have the timestamp as part of the Deserialization Schema, I
would suggest to not add yet another specialized schema, but extend the
KeyedDeserializationSchema with another method that takes the timestamp. We
should make that a default method that calls the existing method and make the
existing method an empty default method.
We could also think about renaming `KeyedDeserializationSchema` to
`RichDeserializationSchema` or so, if that would describe the functionality
better (I am not a native speaker, so would be nice for one to give their
opinion here).
> 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)
