[
https://issues.apache.org/jira/browse/FLINK-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15673238#comment-15673238
]
Manu Zhang commented on FLINK-5061:
-----------------------------------
We will always see elements with timestamp > watermark T. I think the problem
is that T is not available to users in the window function which
[FLIP-2|https://cwiki.apache.org/confluence/display/FLINK/FLIP-2+Extending+Window+Function+Metadata]
tries to solve. If a custom trigger is implemented that fires on watermark but
not necessarily the end of event-time window, the same problem will rise again.
> Remove ContinuousEventTimeTrigger
> ---------------------------------
>
> Key: FLINK-5061
> URL: https://issues.apache.org/jira/browse/FLINK-5061
> Project: Flink
> Issue Type: Improvement
> Components: Streaming
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
> Fix For: 1.2.0
>
>
> The Trigger does not do what people think it does. The problem is that a
> watermark T signals that we won't see elements with timestamp < T in the
> future. It does not signal that we have not yet seen elements with timestamp
> > T. So it cannot really be used to trigger at different stages of processing
> an event-time window.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
