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[] { 10000, now + 10 * 10000 });
to trigger the expiration(TestExternalBatchWindow).
You might want to send another event and test again.
Thanks,
Ralph
On Thu, Apr 28, 2016 at 7:17 PM, Gihan Anuruddha <gi...@wso2.com> wrote:
> 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 50 events to second based external time batch
> stream only 49 events I'm getting. We want to flush that last remaining
> event after some time in order to execute other analytics correctly. Is
> there anyway to achieve this?
>
> Regards,
> Gihan
>
> W.G. Gihan Anuruddha
> Senior Software Engineer | WSO2, Inc.
> M: +94772272595
>
> _______________________________________________
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
