beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tgroh <>
Subject [GitHub] beam pull request #3647: [BEAM-2566] Remove References to CloudObject from t...
Date Wed, 26 Jul 2017 22:51:14 GMT
GitHub user tgroh opened a pull request:

    [BEAM-2566] Remove References to CloudObject from the Java Harness

    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
    Migrates to using the shared Runner API definitions.

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

    $ git pull rm_cloud_object

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 #3647
commit 0119570cdfc855f182cd0e5650e5f2b22e11b3d6
Author: Thomas Groh <>
Date:   2017-07-26T22:34:23Z

    Remove References to CloudObject from the Java Harness
    Migrates to using the shared Runner API definitions.


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