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

Posted to commits@beam.apache.org by "Ilya Ganelin (JIRA)" <ji...@apache.org> on 2016/05/23 22:20:12 UTC

[jira] [Commented] (BEAM-31) When triggers are changed via pipeline update, stale finished triggers data applied

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

Ilya Ganelin commented on BEAM-31:
----------------------------------

This is marked as duplicated by BEAM-179, which is resolved - can this be closed?

> When triggers are changed via pipeline update, stale finished triggers data applied
> -----------------------------------------------------------------------------------
>
>                 Key: BEAM-31
>                 URL: https://issues.apache.org/jira/browse/BEAM-31
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-core
>            Reporter: Kenneth Knowles
>              Labels: Triggers, Update
>
> TriggerRunner tracks which trigger subexpresions are finished. When the trigger expession is updated via pipeline update, this data is applied arbitrarily to the new trigger expression.
> Implementation note: trigger subexpressions are identified by number, and their finished state stored in a bit set.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)