beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kennknowles <>
Subject [GitHub] incubator-beam pull request #1523: [BEAM-1038] Allow stateful DoFn in Datafl...
Date Tue, 06 Dec 2016 22:31:40 GMT
GitHub user kennknowles opened a pull request:

    [BEAM-1038] Allow stateful DoFn in DataflowRunner

    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](
    Confirmed that the post commit should succeed, via the following command:
    mvn verify \
        --batch-mode \
        --errors \
        --projects runners/google-cloud-dataflow-java \
        -DforkCount=0 \
        -DfailIfNoTests=false \
        -Dtest=org.apache.beam.sdk.transforms.ParDoTest \
            "--tempRoot=..." ]'
    with output ending in:
    Running org.apache.beam.sdk.transforms.ParDoTest
    Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 273.736 sec - in org.apache.beam.sdk.transforms.ParDoTest

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

    $ git pull DataflowRunner-state

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 #1523
commit 9e4d40731ff53b2cd0f2a57d18c6f560db441483
Author: Kenneth Knowles <>
Date:   2016-12-06T21:51:19Z

    Allow stateful DoFn in DataflowRunner


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