flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3375) Allow Watermark Generation in the Kafka Source
Date Wed, 13 Apr 2016 08:51:25 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15238878#comment-15238878
] 

Stephan Ewen commented on FLINK-3375:
-------------------------------------

Big parts were committed in
  - 0ac1549ec58c1737a79e5770a171a8b14bed56dc
  - 3c93103d1476cb05ec0c018bfa6876e4ecad38e8

> Allow Watermark Generation in the Kafka Source
> ----------------------------------------------
>
>                 Key: FLINK-3375
>                 URL: https://issues.apache.org/jira/browse/FLINK-3375
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kafka Connector
>    Affects Versions: 1.0.0
>            Reporter: Stephan Ewen
>            Assignee: Kostas Kloudas
>             Fix For: 1.0.0
>
>
> It is a common case that event timestamps are ascending inside one Kafka Partition. Ascending
timestamps are easy for users, because they are handles by ascending timestamp extraction.
> If the Kafka source has multiple partitions per source task, then the records become
out of order before timestamps can be extracted and watermarks can be generated.
> If we make the FlinkKafkaConsumer an event time source function, it can generate watermarks
itself. It would internally implement the same logic as the regular operators that merge streams,
keeping track of event time progress per partition and generating watermarks based on the
current guaranteed event time progress.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message