Hi There are several complaints when Siddhi aggregate outputs its automatically batching the events and hence the output number of events is not consistently reproducible.
E.g. when using from FooStream#window.time(100) select bar, count() as totalReq insert into FooBarStream; In order to fix this issue we thought of improving the internal event chunk "ComplexEventChunk" to have isbatch() property and only batch events when they are batching enabled. Through this when we write batching extensions such as TimeBatch, LengthBatch windows we can explicitly batch the outputs, and it will be more predictable. Regards Suho -- *S. Suhothayan* Technical Lead & Team Lead of WSO2 Complex Event Processor *WSO2 Inc. *http://wso2.com * <http://wso2.com/>* lean . enterprise . middleware *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
