beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ssisk <>
Subject [GitHub] beam pull request #2174: [BEAM-1310] updates to JdbcIO k8 scripts & data loa...
Date Tue, 07 Mar 2017 00:33:49 GMT
GitHub user ssisk opened a pull request:

    [BEAM-1310] updates to JdbcIO k8 scripts & data loading

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [X] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [X] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [X] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [X] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    We have started setting up the k8 cluster & postgres instances, and I had a few small
updates as I got things working. 
    R @jbonofre 
    cc @jasonkuster 

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

    $ git pull jdbc-it-profiles

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 #2174
commit a59aebad8481044714e0ed8532812de263793843
Author: Stephen Sisk <>
Date:   2017-03-06T23:59:31Z

    Jdbc k8 & data loading: add teardown and update names/docs

commit 156018bbdc7769de6095425504d38703a8e81762
Author: Stephen Sisk <>
Date:   2017-03-07T00:01:26Z

    Jdbc k8 script: postgres data store only accessible inside test project


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