beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tgroh <>
Subject [GitHub] incubator-beam pull request: [BEAM-22] Use PushbackSideInputDoFnRu...
Date Mon, 09 May 2016 20:43:05 GMT
GitHub user tgroh opened a pull request:

    [BEAM-22] Use PushbackSideInputDoFnRunner in the InProcessRunner

    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 removes blocking behavior while retrieving Side Inputs in the InProcessRunner.

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

    $ git pull use_pushback_runner

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 #309
commit ffab4b6b22276bf41c9ce4b33d22c44e6d753268
Author: Thomas Groh <>
Date:   2016-04-28T00:27:57Z

    Use PushbackDoFnRunner in the ParDoInProcessEvaluator
    This ensures that the evaluator does not block while processing an input

commit b7d09e14ef749fcd8e773c82b3f9e73f1646eff8
Author: Thomas Groh <>
Date:   2016-04-28T17:12:09Z

    Limit the number of work schedules per MonitorRunnable run
    This ensures that work readded to the queue will not cause the monitor runnable
    to run forever before delivering timers


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message