[
https://issues.apache.org/jira/browse/FLINK-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008446#comment-15008446
]
Aljoscha Krettek commented on FLINK-3024:
-----------------------------------------
Ok, the problem is actually more subtle. The implementation of
ExtractTimestampsOperator can sometimes emit lower watermarks than it emitted
previously, because of the bug in {{trigger}}. This is normally not a problem
since all operators ensure that watermarks are strictly increasing. Only with
dop=1/chaining does to problem occur since there watermarks are directly
forwarded to downstream operators instead of going through the logic that makes
sure watermarks only advance if all upstream watermarks advance (which also
makes sure that the WM does not decrease).
> TimestampExtractor Does not Work When returning Long.MIN_VALUE
> --------------------------------------------------------------
>
> Key: FLINK-3024
> URL: https://issues.apache.org/jira/browse/FLINK-3024
> Project: Flink
> Issue Type: Bug
> Components: Streaming
> Affects Versions: 0.10.0
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
>
> The problem is that {{ExtractTimestampsOperator}} wrongly updates the
> {{currentWatermark}} in the {{trigger}} method. This will interfere with
> values returned from {{extractWatermark}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
