Re: ContinuousProcessingTimeTrigger on empty

2016-07-12 Thread Kostas Kloudas
Hi Xiang, According to your code, you just put all your elements (no splitting by key) into a single infinite window, and you apply your window function every 5min (after the first element had arrived). The combination of the two means that if you have elements arriving at steady pace of 1 ele

Re: ContinuousProcessingTimeTrigger on empty

2016-07-11 Thread Xiang Zhang
Hi Kostas, Yes, so I tried GlobalWindows. Is it possible to trigger every 5 mins on GlobalWindows? From the comments in the source for ContinuousProcessingTimeTrigger, it says: * A {@link Trigger} that continuously fires based on a given time interval as measured by * the clock of the machine on

Re: ContinuousProcessingTimeTrigger on empty

2016-07-11 Thread Kostas Kloudas
Hi Xiang, Currently this is not supported by the trigger provided by Flink, as a window with no data, is a non-existing window for Flink. What you could do is emit periodically dummy elements from your source (so that all windows have at least one element) and make sure that your windowing func