You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Kostas Kloudas (JIRA)" <ji...@apache.org> on 2016/07/07 15:28:11 UTC

[jira] [Closed] (FLINK-3648) Introduce Trigger Test Harness

     [ https://issues.apache.org/jira/browse/FLINK-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kostas Kloudas closed FLINK-3648.
---------------------------------
    Resolution: Fixed

> 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)