ASF GitHub Bot commented on BEAM-25:

GitHub user kennknowles opened a pull request:


    [BEAM-25] Add DoFn.StateId annotation and validation on fields

    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 
    This introduces just the annotation with analysis and validation in 
`DoFnSignature`. To keep reviews small and easy (and happening in parallel with 
other functionality) my plan is to gradually introduce the annotations and 
validation, while rejecting pipelines that actually use them.

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

    $ git pull https://github.com/kennknowles/incubator-beam 

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 #1086
commit 739720655224211dd1759bbe2c52fed7c7ecee47
Author: Kenneth Knowles <k...@google.com>
Date:   2016-10-11T04:16:37Z

    Add DoFn.StateId annotation and validation on fields


> Add user-ready API for interacting with state
> ---------------------------------------------
>                 Key: BEAM-25
>                 URL: https://issues.apache.org/jira/browse/BEAM-25
>             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

Reply via email to