beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vikkyrk <>
Subject [GitHub] incubator-beam pull request #635: BEAM-354: End-to-end tests for V1Beta3 Dat...
Date Tue, 12 Jul 2016 00:26:29 GMT
GitHub user vikkyrk opened a pull request:

    BEAM-354: End-to-end tests for V1Beta3 Datastore

    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](
    - Add end-to-end tests for v1beta3 DatastoreIO
    - Common helper functions are under V1Beta3TestUtils, which contains direct reader and
writer for datastore. 

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

    $ git pull vikasrk/datastoreIOE2ETest

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 #635
commit 3f24cf227b6550a5af7c4497108293981a0c529a
Author: Vikas Kedigehalli <>
Date:   2016-07-11T18:31:48Z

    datastore e2e tests

commit 4e9d7540349337e1e4b576f5e907d7fab1b1e5d4
Author: Vikas Kedigehalli <>
Date:   2016-07-11T23:50:46Z

    Clean up

commit 468124b8887727112b643bd004a82589515b9fae
Author: Vikas Kedigehalli <>
Date:   2016-07-12T00:21:31Z

    Checkstyle and some comments


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