beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From peihe <>
Subject [GitHub] beam pull request #3792: [BEAM-2824]: support PipelineResult.waitUntilFinish...
Date Wed, 30 Aug 2017 07:43:07 GMT
GitHub user peihe opened a pull request:

    [BEAM-2824]: support PipelineResult.waitUntilFinish() in JStormRunner local mode and uses
it in TestJStormRunner.

    Follow this checklist to help us incorporate your contribution quickly and easily:
     - [ ] Make sure there is a [JIRA issue](
filed for the change (usually before you start working on it).  Trivial changes like typos
do not require a JIRA issue.  Your pull request should address just this issue, without pulling
in other changes.
     - [ ] Each commit in the pull request should have a meaningful subject line and body.
     - [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`,
where you replace `BEAM-XXX` with the appropriate JIRA issue.
     - [ ] Write a pull request description that is detailed enough to understand what the
pull request does, how, and why.
     - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will
be performed on your pull request automatically.
     - [ ] If this contribution is large, please file an Apache [Individual Contributor License

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

    $ git pull jstorm-runner-1

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 #3792
commit 18cfc8ecc06d79d14cc9bcd07414a2471725883d
Author: Pei He <>
Date:   2017-08-29T12:10:06Z

    [BEAM-2824]: support PipelineResult.waitUntilFinish() in jstorm local mode.

commit 37bc0bd827ce5612b94d03685cc2ab176c691627
Author: Pei He <>
Date:   2017-08-30T06:50:20Z

    [BEAM-2824] Uses PipelineResult in TestJStormRunner.


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