[
https://issues.apache.org/jira/browse/BEAM-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858140#comment-15858140
]
ASF GitHub Bot commented on BEAM-25:
------------------------------------
GitHub user kennknowles opened a pull request:
https://github.com/apache/beam-site/pull/149
[BEAM-25,BEAM-27] Update the capability matrix for state and timers
The clarity of the model spec for state and timers are at parity with other
model features, and both state and timers are partially supported by the Flink
and Dataflow runners.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kennknowles/incubator-beam-site
state-capabilities
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam-site/pull/149.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #149
----
commit e347f09fe4ff38c03b04434f3e30dd879a8dc9cd
Author: Kenneth Knowles <[email protected]>
Date: 2017-02-08T15:45:18Z
Update the capability matrix for state and timers
----
> Add user-ready API for interacting with state
> ---------------------------------------------
>
> Key: BEAM-25
> URL: https://issues.apache.org/jira/browse/BEAM-25
> Project: Beam
> Issue Type: New Feature
> 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
(v6.3.15#6346)
