Mailing-List: contact commits-help@beam.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@beam.incubator.apache.org
Date: Fri, 4 Nov 2016 18:11:59 +0000 (UTC)
From: "Kenneth Knowles (JIRA)" <jira@apache.org>
To: commits@beam.incubator.apache.org
Message-ID: <JIRA.13008638.1475171372000.193108.1478283119026@Atlassian.JIRA>
In-Reply-To: <JIRA.13008638.1475171372000@Atlassian.JIRA>
References: <JIRA.13008638.1475171372000@Atlassian.JIRA> <JIRA.13008638.1475171372015@arcas>
Subject: [jira] [Updated] (BEAM-694) TriggerTester doesn't test timer
 firings
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 04 Nov 2016 18:12:16 -0000


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

Kenneth Knowles updated BEAM-694:
---------------------------------
    Labels: easy starter  (was: )

> TriggerTester doesn't test timer firings
> ----------------------------------------
>
>                 Key: BEAM-694
>                 URL: https://issues.apache.org/jira/browse/BEAM-694
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-core
>            Reporter: Eugene Kirpichov
>            Priority: Minor
>              Labels: easy, starter
>
> 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)