get trigger context from WindowFunction

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

get trigger context from WindowFunction

Andrew Griess
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 partitioned state can be used so it can be accessed both by a trigger as well as the window function. Knowing the current watermark in the window function would be enough information if that’s easier to accomplish.

Thanks for your help,

Andrew Griess


Reply | Threaded
Open this post in threaded view
|

Re: get trigger context from WindowFunction

Ufuk Celebi
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-FLIP-2-Extending-Window-Function-Metadata-td12522.html

Looping in Aljoscha who worked on this and maybe knows a way to work around it with what we currently have?

– Ufuk

On 14 November 2016 at 01:37:11, Griess, Andrew ([hidden email]) wrote:

> 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 partitioned  
> state can be used so it can be accessed both by a trigger as well as the window function.  
> Knowing the current watermark in the window function would be enough information if  
> that's easier to accomplish.
>  
> Thanks for your help,
>  
> Andrew Griess
>  
>  
>  

Reply | Threaded
Open this post in threaded view
|

Re: get trigger context from WindowFunction

Aljoscha Krettek
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 <[hidden email]> wrote:
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-FLIP-2-Extending-Window-Function-Metadata-td12522.html

Looping in Aljoscha who worked on this and maybe knows a way to work around it with what we currently have?

– Ufuk

On 14 November 2016 at 01:37:11, Griess, Andrew ([hidden email]) wrote:
> 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 partitioned
> state can be used so it can be accessed both by a trigger as well as the window function.
> Knowing the current watermark in the window function would be enough information if
> that's easier to accomplish.
>
> Thanks for your help,
>
> Andrew Griess
>
>
>