I believe we should have separate handler processors for join, pattern & sequence. Here they will subscribe separately to each stream and queue all the data in a single disruptor. Then based on the event correct handler chain will be called. We also need to implement special handlers to do joins and change states, here single instance of the handler will be used by multiple handler chains.
On Wed, Aug 6, 2014 at 8:27 AM, Sachini Jayasekara <[email protected]> wrote: > Hi, > > I think that we have to have a list of handler processors for join cases, > containing first handler processor(which contains Processor Chain) of both > left and right streams of the join query. > Even in patterns I think that we have to have a list of handler processors > containing handler processors of all the streams used for partition query. > WDYT? > > > Here we have to a single join/pattern hander processor which will contain list of SimpleHanderProcessors. may be we can rename SimpleHanderProcessors to StreamHanderProcessor because it will be one per stream. > > > > > > On Tue, Aug 5, 2014 at 7:25 PM, Tishan Dahanayakage <[email protected]> > wrote: > >> Hi, >> While refactoring QueryRuntime to use processor chain concept (Currently >> it was tested by forwarding initial processor (ie. not HandlerProcessor) as >> a list to QueryRuntime and within each HandlerProcessor it is implemented >> to traverse through the Processor chain ) I came across following situation. >> >> >> >> >> Here is a diagram[1] focused on QueryRuntime of above diagram. Here once >> event is received it is converted then forwarded to processor chain then to >> selector. Event Converter is added to the Handler Processor within Query >> Creator currently. All these are inside Handler processor. In this >> architecture we only have to offer a HandlerProcessor to QR not the >> processor chain. Point to clarify is can we extend this architecture when >> implementing joins? If so how? Are we creating Join/Pattern Handler >> Processor separately with replicated Event Converter, Processor Chain duos? >> Need to finalize this so that we can decide what QR can expect after >> constructing a query. (Ex: a Handler Processor/List of Handler Processor, >> etc) >> >> [1] >> https://docs.google.com/a/wso2.com/drawings/d/1reCrHPRpJQUIh5bWQGrKhr0JM--F4dOEfTLCz8tLQec/edit?usp=sharing >> >> >> >> On Mon, Jul 28, 2014 at 4:47 PM, Sriskandarajah Suhothayan <[email protected] >> > wrote: >> >>> >>> >>> -- >>> >>> *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 <%28%2B94%29%20779%20756%20757> | 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>* >>> >> >> >> >> -- >> Tishan Dahanayakage >> Software Engineer >> WSO2, Inc. >> Mobile:+94 716481328 >> >> Disclaimer: This communication may contain privileged or other >> confidential information and is intended exclusively for the addressee/s. >> If you are not the intended recipient/s, or believe that you may have >> received this communication in error, please reply to the sender indicating >> that fact and delete the copy you received and in addition, you should not >> print, copy, re-transmit, disseminate, or otherwise use the information >> contained in this communication. Internet communications cannot be >> guaranteed to be timely, secure, error or virus-free. The sender does not >> accept liability for any errors or omissions. >> > > > > -- > > > > *Thanks & Regards,Sachini Jayasekara Software Engineer; **WSO2 Inc. * > > *lean . enterprise . middleware | http://wso2.com <http://wso2.com> * > -- *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 <%28%2B94%29%20779%20756%20757> | 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
