[
https://issues.apache.org/jira/browse/FLINK-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461953#comment-16461953
]
Fred Teunissen commented on FLINK-8500:
---------------------------------------
Both approaches will work, but we have to choose. The first approach exposes
the Kafka API as part of the Flink API. The second approach hides the Kafka API
but will require a bit more resources to maintain. The second approach would
have my vote.
I don’t want to introduce scope creep, but I think there are more input sources
that could benefit from a more generic (de)serialization scheme. Should we look
into that, or leave it for now (in issues 5479 the idea of a `common connector
framework` is mentioned, should it be picked up there)?
> 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)
