GitHub user tgroh opened a pull request: https://github.com/apache/incubator-beam/pull/322
[BEAM-22] More regularly schedule additional roots 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](https://www.apache.org/licenses/icla.txt). --- This ensures that even when elements are pushed back into the Pipeline Runner, roots are scheduled if necessary. As elements may be rescheduled indefinitely, this is required to ensure that unbounded roots are scheduled during pipeline execution when existing elements are blocked on side inputs. You can merge this pull request into a Git repository by running: $ git pull https://github.com/tgroh/incubator-beam more_aggressively_add_roots Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-beam/pull/322.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #322 ---- commit 1f5e399630e3ba71e2c025e7ab3f32c6c3ba9518 Author: Thomas Groh <tg...@google.com> Date: 2016-05-11T00:11:23Z More regularly schedule additional roots This ensures that even when elements are pushed back into the Pipeline Runner, roots are scheduled if necessary. As elements may be rescheduled indefinitely, this is required to ensure that unbounded roots are scheduled during pipeline execution when existing elements are blocked on side inputs. ---- --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---