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

Posted to commits@beam.apache.org by "Daniel Halperin (JIRA)" <ji...@apache.org> on 2017/04/03 17:16:41 UTC

[jira] [Assigned] (BEAM-987) TestStream.advanceWatermarkToInfinity should perhaps also advance processing time

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

Daniel Halperin reassigned BEAM-987:
------------------------------------

    Assignee:     (was: Thomas Groh)

> TestStream.advanceWatermarkToInfinity should perhaps also advance processing time
> ---------------------------------------------------------------------------------
>
>                 Key: BEAM-987
>                 URL: https://issues.apache.org/jira/browse/BEAM-987
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-direct, testing
>            Reporter: Eugene Kirpichov
>
> I ran into this when writing a test for Splittable DoFn whose input was a TestStream. I constructed a TestStream that didn't call advanceProcessingTime, and as a result, the SDF's timers didn't fire and the test got stuck.
> I think the meaning of "advanceWatermarkToInfinity" is "don't add any more elements to the stream and see what happens eventually", and "eventually" includes "eventually in processing time domain", not just in event-time domain (watermark).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)