beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tgroh <>
Subject [GitHub] incubator-beam pull request: Uniformly apply toLowerCase for Dataf...
Date Fri, 15 Apr 2016 17:07:49 GMT
GitHub user tgroh opened a pull request:

    Uniformly apply toLowerCase for Dataflow Job Names

    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](
    Also do minor cleanup of DataflowPIpelineOptions.

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

    $ git pull stop_lowercase

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 #187
commit 511ed61dc7d4e15c5e493a931d7e15b94d3b005c
Author: Thomas Groh <>
Date:   2016-04-15T17:05:36Z

    Enforce JobName Preconditions in the Dataflow Runner
    This ensures that whenever a DataflowPipelineRunner is created, the
    jobName of the created options conforms to the requirements of the
    Dataflow Service.

commit 2edc88931472d7e38e26a117a7707417ff879e51
Author: Thomas Groh <>
Date:   2016-04-15T17:06:21Z

    Clean up DataflowPipeline[Debug]Options
    getUpdate should be isUpdate, to meet standard JavaBeans style.
    Remove deprecated update property from DataflowPipelineDebugOptions


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