flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3648) Introduce Trigger Test Harness
Date Thu, 07 Jul 2016 15:26:10 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366268#comment-15366268

ASF GitHub Bot commented on FLINK-3648:

Github user aljoscha commented on the issue:

    Thanks for your work. 😃 I merged it. Could you please take care of closing this PR
and the issue?

> 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

View raw message