[
https://issues.apache.org/jira/browse/BEAM-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Groh resolved BEAM-156.
------------------------------
Resolution: Fixed
Fix Version/s: 0.3.0-incubating
The DirectRunner drives progress via quiescence. Although it does not pass an
explicit flag that the pipeline has quiesced, it will only invoke root
transforms if no progress can be made with the elements currently in the
Pipeline.
> Implement Quiescence Signalling in the InProcessPipelineRunner
> --------------------------------------------------------------
>
> Key: BEAM-156
> URL: https://issues.apache.org/jira/browse/BEAM-156
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Thomas Groh
> Assignee: Thomas Groh
> Fix For: 0.3.0-incubating
>
>
> A pipeline is quiescent when the following two properties hold:
> There are no triggers that can fire, given the current processing time and
> watermark
> All pending elements cannot make progress until a side input produces
> additional output
> This is approximately equivalent to: If no more input is received, the
> pipeline will not perform any additional processing absent advances in
> processing time or event time
> See also:
> https://docs.google.com/document/d/1fZUUbG2LxBtqCVabQshldXIhkMcXepsbv2vuuny8Ix4/edit#
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
