beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bjchambers <>
Subject [GitHub] incubator-beam pull request #529: [BEAM-390] Remove many additional definiti...
Date Fri, 24 Jun 2016 06:23:21 GMT
GitHub user bjchambers opened a pull request:

    [BEAM-390] Remove many additional definitions/uses of .named methods

    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](

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

    $ git pull beam-390-named-2

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 #529
commit dc3f4f96b172b5bda53b68c639f7e5c1a7d1df68
Author: Ben Chambers <>
Date:   2016-06-24T00:55:24Z

    Remove many definitions of named methods
    Specifically, remove the occurrences in:
      - Window
      - AvroIO
      - PubsubIO
      - TextIO
      - BigQueryIO
      - Read

commit 96dcd4787a96b04ceeb50a2685295e9e1d8b6f71
Author: Ben Chambers <>
Date:   2016-06-24T05:27:05Z

    Remove many uses of .named methods
    Specifically, remove uses of:
      - Window.named
      - AvroIO.named
      - PubSubIO.named
      - TextIO.named
      - BigQueryIO.named
      - Read.named


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