[
https://issues.apache.org/jira/browse/FLINK-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863299#comment-15863299
]
ASF GitHub Bot commented on FLINK-4616:
---------------------------------------
Github user MayerRoman commented on the issue:
https://github.com/apache/flink/pull/3031
I hope that I ended up with another issue, and I come back to this.
First, I want to ask a question that perhaps remove all the others.
Tzu-Li Tai, did I understand correctly that if discussion about letting the
window operators checkpoint watermarks lead to the decision to implement this
functionality in the window operators, the need to preserve the state of
watermarks in Kafka consumer will disappear?
> Kafka consumer doesn't store last emmited watermarks per partition in state
> ---------------------------------------------------------------------------
>
> Key: FLINK-4616
> URL: https://issues.apache.org/jira/browse/FLINK-4616
> Project: Flink
> Issue Type: Bug
> Components: Kafka Connector
> Affects Versions: 1.1.1
> Reporter: Yuri Makhno
> Assignee: Roman Maier
>
> Kafka consumers stores in state only kafka offsets and doesn't store last
> emmited watermarks, this may go to wrong state when checkpoint is restored:
> Let's say our watermark is (timestamp - 10) and in case we have the following
> messages queue results will be different after checkpoint restore and during
> normal processing:
> A(ts = 30)
> B(ts = 35)
> ------ checkpoint goes here
> C(ts=15) -- this one should be filtered by next time window
> D(ts=60)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
