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-25) Add user-ready API for interacting with state
Date Tue, 04 Oct 2016 18:54:20 GMT


ASF GitHub Bot commented on BEAM-25:

GitHub user kennknowles opened a pull request:

    [BEAM-25] Refactor StateSpec out of StateTag

    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`
     - [ ] 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](
    R: @aljoscha AND @tgroh AND @bjchambers 
    This is a rebase of #793 without much cleanup. The same commentary applies - I'm not totally
happy with it but I want to ask for feedback.

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

    $ git pull StateSpec

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 #1044
commit 1f2de1e1212cbdb5eb3c8cb7caf30b94da5e0b00
Author: Kenneth Knowles <>
Date:   2016-08-05T03:50:28Z

    Create StateSpec parallel to StateTag

commit 6fa680858719eaf13edcc08aa3f3260584876fb5
Author: Kenneth Knowles <>
Date:   2016-08-05T04:48:48Z

    Make StateTag carry a StateSpec separately from its id


> Add user-ready API for interacting with state
> ---------------------------------------------
>                 Key: BEAM-25
>                 URL:
>             Project: Beam
>          Issue Type: Sub-task
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>              Labels: State
> Our current state API is targeted at runner implementers, not pipeline authors. As such
it has many capabilities that are not necessary nor desirable for simple use cases of stateful
ParDo (such as dynamic state tag creation). Implement a simple state intended for user access.
> (Details of our current thoughts in forthcoming design doc)

This message was sent by Atlassian JIRA

View raw message