Re: [Dev] [CEP][Siddhi QL] Flushing external time batch after some time

2016-04-29 Thread Sriskandarajah Suhothayan
Thanks for the input Ralph Su Suho On Fri, Apr 29, 2016 at 8:33 AM, Liangfei.Su wrote: > The external time could not be expired if no following events comes in, > only the system time window able to provide auto-expire. Actually, to test > this feature, i write something like > > // to trigger

Re: [Dev] [CEP][Siddhi QL] Flushing external time batch after some time

2016-04-28 Thread Liangfei.Su
The external time could not be expired if no following events comes in, only the system time window able to provide auto-expire. Actually, to test this feature, i write something like // to trigger second round input.send(new Object[] { 1, now + 10 * 1 }); to trigger the expiration(TestEx

Re: [Dev] [CEP][Siddhi QL] Flushing external time batch after some time

2016-04-28 Thread Sriskandarajah Suhothayan
I think the problem is that you are sending only 50 events, but thats will not be the case in real world. Here I think the last event is still in the window as its waiting for next event to check for expiration, without another event arriving it does not know the current running time of the system

[Dev] [CEP][Siddhi QL] Flushing external time batch after some time

2016-04-28 Thread Gihan Anuruddha
Hi All, We are using external time windows in second based and minute based to do some aggregate operations as below. from tempDecompressedEventStream#window.externalTimeBatch(startTime, 1 sec, 0) ​As we observed, this will not flush the current values after some time. As an example, if I send 5