You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Andrew Crites (Jira)" <ji...@apache.org> on 2020/02/11 19:28:00 UTC
[jira] [Commented] (BEAM-9293) Python direct runner doesn't emit
empty pane when it should
[ https://issues.apache.org/jira/browse/BEAM-9293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034763#comment-17034763 ]
Andrew Crites commented on BEAM-9293:
-------------------------------------
And actually, there should be an empty pane emitted for [0, 15) at time 315 too since the default trigger has late=Repeat(Count(1)) so the 'late' element will get emitted right away.
> Python direct runner doesn't emit empty pane when it should
> -----------------------------------------------------------
>
> Key: BEAM-9293
> URL: https://issues.apache.org/jira/browse/BEAM-9293
> Project: Beam
> Issue Type: Bug
> Components: runner-direct
> Reporter: Andrew Crites
> Priority: Minor
>
> In test_stream_test.py, the test test_gbk_execution_no_triggers there is positive allowed_lateness. So the two windows [15, 30) and [300, 315) that do not have late data should have an empty pane emitted when window finishes (after allowed lateness) since the default ClosingBehavior in Python is EMIT_ALWAYS (see transforms/core.py).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)