beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vikkyrk <>
Subject [GitHub] incubator-beam pull request #499: [BEAM-354]: Modify DatastoreIO to use the ...
Date Mon, 20 Jun 2016 18:41:43 GMT
GitHub user vikkyrk opened a pull request:

    [BEAM-354]: Modify DatastoreIO to use the v1beta3 API

    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](
    - Use v1beta3 datastore API and remove all v1beta2 dependencies
    - Modify tests to pass. 

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

    $ git pull vikasrk/datastoreIO-v1beta3

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 #499
commit af35d9829581a450245153dbfb7db23f9ed9fff0
Author: Vikas Kedigehalli <>
Date:   2016-06-16T20:57:43Z

    DatastoreIO: Update datastore API to v1beta3

commit 88b34f746e6332aec69cf1c60212971aae0f9fc0
Author: Vikas Kedigehalli <>
Date:   2016-06-20T17:38:43Z

    DatastoreIO: Update comments

commit 834b87394f5834f7c6475032cafaed89be977ecb
Author: Vikas Kedigehalli <>
Date:   2016-06-20T18:39:14Z

    DatastoreIO: remove unused imports


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