beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-156) Implement Quiescence Signalling in the InProcessPipelineRunner
Date Wed, 27 Jul 2016 23:56:20 GMT


ASF GitHub Bot commented on BEAM-156:

GitHub user tgroh opened a pull request:

    Use AutoValue for StepTransformResult

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    This is a cleanup PR for future changes to StepTransformResult, primarily as part of

You can merge this pull request into a Git repository by running:

    $ git pull step_transform_result_autovalue

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #746
commit c1f66b67c82e149ef27d19c88993b0ab15d19b35
Author: Thomas Groh <>
Date:   2016-07-26T16:38:13Z

    Use AutoValue for StepTransformResult


> Implement Quiescence Signalling in the InProcessPipelineRunner
> --------------------------------------------------------------
>                 Key: BEAM-156
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Thomas Groh
>            Assignee: Thomas Groh
> 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:

This message was sent by Atlassian JIRA

View raw message