[GitHub] [beam] damccorm opened a new issue, #17833: In TriggerRunner, avoid reading the set of finished subtriggers when no subtrigger ever finishes.

[GitBox <gi...@apache.org>]

damccorm opened a new issue, #17833:
URL: https://github.com/apache/beam/issues/17833

   For a trigger expression, TriggerRunner tracks which of the subexpressions have finished to track which subexpression is the currently active trigger that determines when output is permitted. For some triggers (such as the default trigger) this information is not needed. The reads and writes of this data can be elided.
   
   Imported from Jira [BEAM-30](https://issues.apache.org/jira/browse/BEAM-30). Original Jira may contain additional context.
   Reported by: kenn.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [beam] damccorm closed issue #17833: In TriggerRunner, avoid reading the set of finished subtriggers when no subtrigger ever finishes.

[GitBox <gi...@apache.org>]

damccorm closed issue #17833: In TriggerRunner, avoid reading the set of finished subtriggers when no subtrigger ever finishes.
URL: https://github.com/apache/beam/issues/17833


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org