Hi Charini, A great thought!
Would it be possible for you to explain this requirement with an example written in Siddhi? Specifically how to generate a custom event on the timeout. Thanks On Monday, July 11, 2016, Charini Nanayakkara <chari...@wso2.com> wrote: > Hi All, > > I have planned to improve the current implementation of external time > batch window, to allow accepting first event's time as start time, when > specifying a timeout. > > In the current implementation, the 3rd parameter allows user to provide a > user defined start time (whereas the default is to use first event's time > as start time). This value is required to be a constant. The 4th parameter > is reserved for specifying a timeout, which is valuable in an instance > where output needs to be given if events don't arrive for some time. > However, this implementation disallows a user to use the default start time > (first event's start time) and timeout together. > > Therefore, I intend to change the implementation such that user can either > provide a variable or a constant as 3rd parameter. This enables the > external time field to be given as 3rd parameter, from which Siddhi can > retrieve 1st event's time to be used as start time. Alternatively, a > constant value could be given if user defined start time is required. > > Suggestions and comments are most welcome. > > Thank you > Charini > > -- > Charini Vimansha Nanayakkara > Software Engineer at WSO2 > Mobile: 0714126293 > > -- *Imesh Gunaratne* Software Architect WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: https://medium.com/@imesh TW: @imesh
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
