beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-1340) Remove or make private public bits of the SDK that shouldn't be public
Date Wed, 03 May 2017 22:14:04 GMT


ASF GitHub Bot commented on BEAM-1340:

GitHub user kennknowles opened a pull request:

    [BEAM-1340,BEAM-1345] Tighten the Dataflow runner's API surface

    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`.
     - [ ] 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 DataflowRunner-surface

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 #2872
commit 5a8b617d966427adfd2c6e4e05b99991a63ffdb7
Author: Kenneth Knowles <>
Date:   2017-05-03T21:30:55Z

    Tighten the Dataflow runner's API surface


> Remove or make private public bits of the SDK that shouldn't be public
> ----------------------------------------------------------------------
>                 Key: BEAM-1340
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core, sdk-java-extensions
>            Reporter: Kenneth Knowles
>            Priority: Blocker
>              Labels: backward-incompatible
>             Fix For: First stable release
> This JIRA is for the many small changes that do not merit their own JIRA towards getting
the SDK's API surface right. For example, removal of `DoFn.InputProvider` and `DoFn.OutputReceiver`.
> While the above is not quite backwards incompatible, succeeding at this task surely will

This message was sent by Atlassian JIRA

View raw message