Yup, we're currently working on getting ProcessWindowFunction into master.
Then we would work on getting additional information available, such as the
current watermark or a firing reason.
On Mon, 14 Nov 2016 at 11:07 Ufuk Celebi wrote:
> I don't think that this is possible right now.
>
> There
I don't think that this is possible right now.
There are a proposal and discussion to extend the window function meta data
here:
https://cwiki.apache.org/confluence/display/FLINK/FLIP-2+Extending+Window+Function+Metadata
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-FL
Hi Flink Community,
I have a question about knowing what triggered a window when a window function
is executed. We have a case were multiple triggers can fire on a window and it
would be helpful to understand which trigger is was once the window function is
called. I'm not sure if there's a way
