beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Halperin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-987) TestStream.advanceWatermarkToInfinity should perhaps also advance processing time
Date Thu, 01 Dec 2016 21:51:00 GMT

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

Daniel Halperin updated BEAM-987:
---------------------------------
    Component/s: testing
                 runner-direct

> 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
>            Assignee: Thomas Groh
>
> 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.4#6332)

Mime
View raw message