beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From JingsongLi <>
Subject [GitHub] beam pull request #3309: [Beam-1483] Support SetState in Flink runner
Date Wed, 07 Jun 2017 07:42:11 GMT
GitHub user JingsongLi opened a pull request:

    [Beam-1483] Support SetState in Flink runner

    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 BEAM-1483

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 #3309
commit a7f73f6d19da2e21bd2cdd0e95e0d5262a439623
Author: JingsongLi <>
Date:   2017-06-07T06:34:25Z

    Use CoderTypeSerializer and remove unuse code in FlinkStateInternals

commit 70e124f29fb587543c53025050a09883b993db29
Author: JingsongLi <>
Date:   2017-06-07T06:40:30Z

    [BEAM-1483] Support SetState in Flink runner

commit bb97f7fb6c2d11e84dbf6096db748f480327823b
Author: JingsongLi <>
Date:   2017-06-07T07:30:27Z

    Fix MapState return empty Iterable instead of null

commit 77b457ef7f91f5a765727a31c8cbd08ebd29f3c6
Author: JingsongLi <>
Date:   2017-06-07T07:32:54Z

    Update FlinkStateInternalsTest and add setState mapState test


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