beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From evindj <>
Subject [GitHub] beam pull request #3533: [Beam-2230] ApiSurface Refactoring
Date Mon, 10 Jul 2017 12:04:14 GMT
GitHub user evindj opened a pull request:

    [Beam-2230] ApiSurface Refactoring

    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`.
     - [ ] 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](

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

    $ git pull BEAM-2230

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 #3533
commit a0a90f298a5c3131a887193cccb278fbf45e61b5
Author: Innocent Djiofack <>
Date:   2017-07-10T04:30:46Z

    Made ApiSurface abstract and created implementing subclasses

commit c800fb95b7f9a622f4a9dc2fa061764610739298
Author: Innocent Djiofack <>
Date:   2017-07-10T05:34:18Z

    Created the direct runner api surface sub class

commit a532663cf2650d0f5dfbc6ea7838e3c5da77a1bb
Author: Innocent Djiofack <>
Date:   2017-07-10T05:52:22Z

    Modified GcpApiSurface to reflect the correct Api Surface

commit d696b2323bcf89d9272bed94c860dac091bffe3d
Author: Innocent Djiofack <>
Date:   2017-07-10T06:02:03Z

    Fixed Core Google Cloud API surface.

commit 4a321dc4e07087d0fc4148268f83552fa5b65be6
Author: Innocent Djiofack <>
Date:   2017-07-10T11:25:08Z

    Fixed a bug in GcpApiSurface


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