Hi, Is there no valid usecase for users wanting do a 'temporal search' as was in the unintended discussion? ... :-)
I mean would they want to search for a particular event that occurred after matching of another event? Maybe it is not a valid usecase in the context of BAM. Just voicing my thoughts here... :-) Thanks, Lasantha On 26 July 2013 05:25, Hasitha Hiranya <[email protected]> wrote: > Hi, > > +1 for new event search UI. It brings flexibility. > Is this a "read-only" view? What if somebody want to do a query and > remove all the data found? Is it not valid a use-case? > > Thanks > > > On Thu, Jul 25, 2013 at 7:23 PM, Inosh Goonewardena <[email protected]>wrote: > >> I have attached modified mock screens. Appreciate your feedbacks >> >> >> On Thu, Jul 25, 2013 at 5:41 PM, Srinath Perera <[email protected]> wrote: >> >>> ah sorry :) >>> >>> --Srinath >>> >>> >>> On Thu, Jul 25, 2013 at 5:40 PM, Anjana Fernando <[email protected]>wrote: >>> >>>> Hi Srinath, >>>> >>>> I think we got the term "ordering" confused here :) .. I wasn't really >>>> talking about temporal ordering of the events there (I think we can ignore >>>> that for the initial version of search) .. I was mentioning how we properly >>>> give the ordering of the conditions there .. as in the "and", "or" >>>> operators .. like we can say "A and B or C", where by usual operator >>>> precedence it'll be (A and B) or C .. but we may also want to give >>>> something like "A and (B or C)" .. I was just mentioning the syntax we will >>>> need to show the mentioned behavior, we can't do it in a simple way in an >>>> UI. >>>> >>>> Cheers, >>>> Anjana. >>>> >>>> >>>> On Thu, Jul 25, 2013 at 5:27 PM, Srinath Perera <[email protected]>wrote: >>>> >>>>> Hi Anjana, >>>>> >>>>> For example, stream1.prop1="1" -> stream2.prop1="1" to show the >>>>> ordering (note the arrow). >>>>> >>>>> Actually, this is the CEP event pattern format ( >>>>> http://wso2.com/library/articles/2013/06/understanding-siddhi-powers-wso2-cep-2x, >>>>> see sequence). >>>>> IMHO, if we need to show temporal ordering, CEP has the format. May >>>>> be there is room to improve, but in which case we fix both. >>>>> >>>>> Sinthuja, the model we give to end users is EventStreams. IMHO, it is >>>>> best to let him search thinking event steam instead of row Cassandra. >>>>> >>>>> --Srinath >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Thu, Jul 25, 2013 at 4:30 PM, Anjana Fernando <[email protected]>wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> In the search, the part where we give the conditions, this approach >>>>>> doesn't handle the ordering of the conditions, like (stream1.prop1="1" or >>>>>> stream2.prop2="2") and (stream1.prop3="3") kind of a scenario. So how >>>>>> about >>>>>> having a simple search query format instead and just give a search text >>>>>> field to do the queries? .. I guess we can use a format like the one I >>>>>> just >>>>>> mentioned for the earlier example. >>>>>> >>>>>> Cheers, >>>>>> Anjana. >>>>>> >>>>>> >>>>>> On Thu, Jul 25, 2013 at 4:03 PM, Srinath Perera <[email protected]>wrote: >>>>>> >>>>>>> 1) For Event search, user need to pick an stream, then he can >>>>>>> search. Given we have activity search I think that would do. >>>>>>> >>>>>>> 2) For activity search, this only handle a small subset. One >>>>>>> activity might have events from many streams. We define property search >>>>>>> to >>>>>>> match if at least one event in an activity matches the given condition >>>>>>> (e.g. property). If user need more complex ones (e.g. temporal >>>>>>> conditions) >>>>>>> they should define and KPI. >>>>>>> >>>>>>> --Srinath >>>>>>> >>>>>>> >>>>>>> On Thu, Jul 25, 2013 at 3:54 PM, Inosh Goonewardena >>>>>>> <[email protected]>wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> We had a few discussion sessions with Srinath about BAM events >>>>>>>> search and activity search. >>>>>>>> >>>>>>>> Herewith I have attached mock up screens on how the search UIs will >>>>>>>> be like. Any feedback is appreciated. >>>>>>>> >>>>>>>> -- >>>>>>>> Regards, >>>>>>>> >>>>>>>> Inosh Goonewardena >>>>>>>> Associate Technical Lead- WSO2 Inc. >>>>>>>> Mobile: +94779966317 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> ============================ >>>>>>> Srinath Perera, Ph.D. >>>>>>> http://people.apache.org/~hemapani/ >>>>>>> http://srinathsview.blogspot.com/ >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Anjana Fernando* >>>>>> Technical Lead >>>>>> WSO2 Inc. | http://wso2.com >>>>>> lean . enterprise . middleware >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> ============================ >>>>> Srinath Perera, Ph.D. >>>>> Director, Research, WSO2 Inc. >>>>> Visiting Faculty, University of Moratuwa >>>>> Member, Apache Software Foundation >>>>> Research Scientist, Lanka Software Foundation >>>>> Blog: http://srinathsview.blogspot.com/ >>>>> Photos: http://www.flickr.com/photos/hemapani/ >>>>> Phone: 0772360902 >>>>> >>>> >>>> >>>> >>>> -- >>>> *Anjana Fernando* >>>> Technical Lead >>>> WSO2 Inc. | http://wso2.com >>>> lean . enterprise . middleware >>>> >>> >>> >>> >>> -- >>> ============================ >>> Srinath Perera, Ph.D. >>> Director, Research, WSO2 Inc. >>> Visiting Faculty, University of Moratuwa >>> Member, Apache Software Foundation >>> Research Scientist, Lanka Software Foundation >>> Blog: http://srinathsview.blogspot.com/ >>> Photos: http://www.flickr.com/photos/hemapani/ >>> Phone: 0772360902 >>> >> >> >> >> -- >> Regards, >> >> Inosh Goonewardena >> Associate Technical Lead- WSO2 Inc. >> Mobile: +94779966317 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Hasitha Abeykoon* > > Software Engineer; WSO2, Inc.; http://wso2.com > *cell:* *+94 719363063* > *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>* * > * > * > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: [email protected] mobile: (+94) 71 5247551
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
