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

Posted to issues@beam.apache.org by "Danny McCormick (Jira)" <ji...@apache.org> on 2022/06/04 22:31:00 UTC

[jira] [Commented] (BEAM-13076) Python AfterAny, AfterAll do not follow spec

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

Danny McCormick commented on BEAM-13076:
----------------------------------------

This issue has been migrated to https://github.com/apache/beam/issues/21262

> Python AfterAny, AfterAll do not follow spec
> --------------------------------------------
>
>                 Key: BEAM-13076
>                 URL: https://issues.apache.org/jira/browse/BEAM-13076
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py-core
>            Reporter: Zachary Houfek
>            Priority: P1
>
> Both AfterAll and AfterAny should complete after firing, but they base their logic on the subtriggers, but they instead only finish if all the fired subtriggers or any of the fired subtriggers finish. This makes it possible for them to never finish.
> For more info, see discussion in https://github.com/apache/beam/pull/15603



--
This message was sent by Atlassian Jira
(v8.20.7#820007)