[
https://issues.apache.org/jira/browse/FLINK-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362266#comment-15362266
]
ASF GitHub Bot commented on FLINK-3648:
---------------------------------------
GitHub user kl0u opened a pull request:
https://github.com/apache/flink/pull/2199
[FLINK-3648] Introduce Trigger Test Harness
Adds a test harness that facilitates the testing of custom triggers and
window assigners.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kl0u/flink trigger_testin
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2199.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 #2199
----
commit 1679efb0c9d97d4596be75671adc15ffa3cf90db
Author: kl0u <[email protected]>
Date: 2016-07-04T10:21:55Z
[FLINK-3648] Introduce Trigger Test Harness
----
> Introduce Trigger Test Harness
> ------------------------------
>
> Key: FLINK-3648
> URL: https://issues.apache.org/jira/browse/FLINK-3648
> Project: Flink
> Issue Type: Sub-task
> Components: Streaming
> Reporter: Aljoscha Krettek
> Assignee: Kostas Kloudas
>
> As mentioned in
> https://docs.google.com/document/d/1Xp-YBf87vLTduYSivgqWVEMjYUmkA-hyb4muX3KRl08/edit#
> we should build on the processing-time clock introduced in FLINK-3646 and
> add a testing harness for triggers. The harness should allow inputting
> elements, updating watermark, updating processing-time and firing timers. The
> output of the trigger as well as state managed by the partitioned state
> abstraction should be observable to verify correct trigger behavior.
> Then, we should add tests for all triggers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
