[
https://issues.apache.org/jira/browse/FLINK-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690407#comment-15690407
]
ASF GitHub Bot commented on FLINK-5061:
---------------------------------------
Github user mxm commented on the issue:
https://github.com/apache/flink/pull/2803
I just opened a PR as well :)
I was under the assumption that a continuous trigger is useful for early
window results. Not sure if it might be confusing for users because you can
receive elements newer than the current Watermark.
> 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
>
> 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)
