Sure, I also thought about this but went for the "extreme" initially. If no-one objects I'll update the doc in a bit.
On Wed, 13 Jul 2016 at 14:17 Stephan Ewen <se...@apache.org> wrote: > Thanks for opening this. > > I see the need for having an extensible context object for window function > invocations, but i think hiding every parameter in the context is a bit > unnatural. > > How about having a function "apply(Key, Values, WindowContext, Collector)" > ? > It should be possible to write the straightforward use cases without > accessing the context object. > > > > On Wed, Jul 13, 2016 at 1:56 PM, Aljoscha Krettek <aljos...@apache.org> > wrote: > > > Hi, > > this is a proposal to introduce a new interface for the window function > to > > make it more extensible for the future where we might want to provide > > additional information about why a window fired to the user function: > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-2+Extending+Window+Function+Metadata > > > > I'd appreciate your thoughts! > > > > Cheers, > > Aljoscha > > >
