+1
Etienne
Le 28/03/2017 à 22:27, Kenneth Knowles a écrit :
Hi all,
I have a little extension to the stateful DoFn annotations to circulate for
feedback: Allow a method to be annotated with @OnWindowExpiration to
automatically get a callback at some point after the window has expired,
but bef
+1
Regards
JB
On 03/28/2017 10:27 PM, Kenneth Knowles wrote:
Hi all,
I have a little extension to the stateful DoFn annotations to circulate for
feedback: Allow a method to be annotated with @OnWindowExpiration to
automatically get a callback at some point after the window has expired,
but bef
> >
> > > > > 1. Expire the window and start dropping any more input
> > > > > 2. Fire the user's expiration callback
> > > > > 3. Delete the state for the window
> > > > >
> > > > > This actually made me think of a sp
allback
> > > > 3. Delete the state for the window
> > > >
> > > > This actually made me think of a special property of
> @OnWindowExpiration:
> > > > we can forbid Timer parameters. If we followed Robert's idea we
> could do
> > &
ation callback
> > > 3. Delete the state for the window
> > >
> > > This actually made me think of a special property of @OnWindowExpiration:
> > > we can forbid Timer parameters. If we followed Robert's idea we could do
> > > static analysis and en
al feature. It is more than
> > convenience.
> >
> > Kenn
> >
> >
> > >
> > --From:Kenneth
> > > Knowles Time:2017 Mar 29 (Wed) 09:07To:dev <
> > > dev@beam.apache.org>Sub
---------
> --From:Kenneth
> > Knowles Time:2017 Mar 29 (Wed) 09:07To:dev <
> > dev@beam.apache.org>Subject:Re: [PROPOSAL] @OnWindowExpiration
> > On Tue, Mar 28, 2017 at 2:47 PM, Eugene Kirpichov <
> > kirpic...@google.com.
pecial feature. It is more than
convenience.
Kenn
> --From:Kenneth
> Knowles Time:2017 Mar 29 (Wed) 09:07To:dev <
> dev@beam.apache.org>Subject:Re: [PROPOSAL] @OnWindowExpiration
> On Tue, Mar 28, 2017 at 2:47 PM,
--From:Kenneth
Knowles Time:2017 Mar 29 (Wed) 09:07To:dev
Subject:Re: [PROPOSAL] @OnWindowExpiration
On Tue, Mar 28, 2017 at 2:47 PM, Eugene Kirpichov <
kirpic...@google.com.invalid> wrote:
> Kenn, can you quote some use cases for this, to make it more c
On Tue, Mar 28, 2017 at 2:47 PM, Eugene Kirpichov <
kirpic...@google.com.invalid> wrote:
> Kenn, can you quote some use cases for this, to make it more clear what are
> the consequences of having this API in this form?
>
> I recall that one of the main use cases was batching DoFn, right?
>
I beli
Kenn, can you quote some use cases for this, to make it more clear what are
the consequences of having this API in this form?
I recall that one of the main use cases was batching DoFn, right?
On Tue, Mar 28, 2017 at 1:37 PM Kenneth Knowles
wrote:
> On Tue, Mar 28, 2017 at 1:32 PM, Robert Bradsh
On Tue, Mar 28, 2017 at 1:32 PM, Robert Bradshaw <
rober...@google.com.invalid> wrote:
> Another alternative is to be able to set special timers, e.g. end of window
> and expiration of window. That at least addresses (2).
>
Potentially a tangent, but that would perhaps fit in with the idea of
rem
Another alternative is to be able to set special timers, e.g. end of window
and expiration of window. That at least addresses (2).
On Tue, Mar 28, 2017 at 1:27 PM, Kenneth Knowles
wrote:
> Hi all,
>
> I have a little extension to the stateful DoFn annotations to circulate for
> feedback: Allow a
Hi all,
I have a little extension to the stateful DoFn annotations to circulate for
feedback: Allow a method to be annotated with @OnWindowExpiration to
automatically get a callback at some point after the window has expired,
but before the state for the window has been cleared.
Today, a user can
14 matches
Mail list logo
