[
https://issues.apache.org/jira/browse/FLINK-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664059#comment-15664059
]
ASF GitHub Bot commented on FLINK-5061:
---------------------------------------
GitHub user aljoscha opened a pull request:
https://github.com/apache/flink/pull/2803
[FLINK-5061] Remove ContinuousEventTimeTrigger
R: @StephanEwen for review
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aljoscha/flink
remove-continuous-event-time-trigger
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2803.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2803
----
commit b892c68f426c5c198c698746b03a075149d07fc5
Author: Aljoscha Krettek <[email protected]>
Date: 2016-11-14T14:26:38Z
[FLINK-5061] Remove ContinuousEventTimeTrigger
----
> 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)
