beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Groh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-694) TriggerTester doesn't test timer firings
Date Thu, 29 Sep 2016 18:00:24 GMT

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

Thomas Groh updated BEAM-694:
-----------------------------
    Description: 
TriggerTester exposes a `fireIfShouldFire(BoundedWIndow)` method. This is used to prompt a
call to the trigger with the current state of the trigger tester (Input Watermarks, elements
present, etc), and see if the trigger should fire.

The TriggerTester should automatically call back to the trigger with the current state whenever
a Timer fires, as specified by the current watermarks and any Timers set by the trigger under
test. This ensures that Triggers set underlying timers properly, so the trigger will fire
even if no additional elements arrive.

> TriggerTester doesn't test timer firings
> ----------------------------------------
>
>                 Key: BEAM-694
>                 URL: https://issues.apache.org/jira/browse/BEAM-694
>             Project: Beam
>          Issue Type: Bug
>            Reporter: Eugene Kirpichov
>
> TriggerTester exposes a `fireIfShouldFire(BoundedWIndow)` method. This is used to prompt
a call to the trigger with the current state of the trigger tester (Input Watermarks, elements
present, etc), and see if the trigger should fire.
> The TriggerTester should automatically call back to the trigger with the current state
whenever a Timer fires, as specified by the current watermarks and any Timers set by the trigger
under test. This ensures that Triggers set underlying timers properly, so the trigger will
fire even if no additional elements arrive.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message