Hi all, I thought I would loop back on this proposal and email thread with an FYI that coding has begun for this design. Here are some recent PRs for your perusal, if you are interested.
https://github.com/apache/incubator-beam/pull/10 <https://github.com/apache/incubator-beam/pull/1064>44 "Refactor StateSpec out of StateTag https://github.com/apache/incubator-beam/pull/1086 "Add DoFn.StateId annotation and validation on fields" https://github.com/apache/incubator-beam/pull/1102 "Add initial bits for DoFn Timer API" Kenn On Fri, Jul 29, 2016 at 12:26 PM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > +1 > > It sounds very good. > > Regards > JB > > On 07/27/2016 05:20 AM, Kenneth Knowles wrote: > > Hi everyone, > > > > > > I would like to offer a proposal for a much-requested feature in Beam: > > Stateful processing in a DoFn. Please check out and comment on the > proposal > > at this URL: > > > > > > https://s.apache.org/beam-state > > > > > > This proposal includes user-facing APIs for persistent state and timers. > > Together, these provide rich capabilities that have been called "per-key > > workflows", the subject of [BEAM-23]. > > > > > > Note that this proposal has an important prerequisite: a new design for > > DoFn. The new DoFn is strongly motivated by this design for state and > > timers, but we should discuss it separately. I will start a separate > thread > > for that. > > > > > > On this email thread, I'd like to try to focus the discussion on state & > > timers. And of course, please do comment on the particulars in the > document. > > > > > > Kenn > > > > > > [BEAM-23] https://issues.apache.org/jira/browse/BEAM-23 > > > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com >