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

Posted to commits@beam.apache.org by "Aljoscha Krettek (JIRA)" <ji...@apache.org> on 2018/01/26 13:24:00 UTC

[jira] [Commented] (BEAM-3529) Side Input callbacks should fire after a window has expired in addition to when the trigger would fire

    [ https://issues.apache.org/jira/browse/BEAM-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341044#comment-16341044 ] 

Aljoscha Krettek commented on BEAM-3529:
----------------------------------------

There should probably also be {{ValidatesRunner}} tests about this behaviour to ensure that it is uniform across runners, right?

> Side Input callbacks should fire after a window has expired in addition to when the trigger would fire
> ------------------------------------------------------------------------------------------------------
>
>                 Key: BEAM-3529
>                 URL: https://issues.apache.org/jira/browse/BEAM-3529
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-direct
>            Reporter: Thomas Groh
>            Assignee: Thomas Groh
>            Priority: Major
>
> Otherwise a streaming pipeline where elements trying to access a window that has expired will not progress, even though we can be certain that there will never be inputs in that window.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)