Well .. this is not meant to be a Cassandra search .. it's an event/activity search, so we can't expose the underlying data store here and say, we are searching for raw data that's there ..
Cheers, Anjana. On Thu, Jul 25, 2013 at 5:18 PM, Sinthuja Ragendran <[email protected]>wrote: > Hi, > > +1 for Anjana's suggestion for activity search. > > For the event search isn't it better that we make the UI generic for > cassandra data search, rather stream's events search? > > Ie, instead of StreamName we can provide the Columnfamily name, so on. And > version field also can be omitted, if it's required to be considered into > the search criteria, then the user can give that in the property list. > > WDYT? > > Thanks, > Sinthuja. > > > > 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 >> > > > > -- > *Sinthuja Rajendran* > Software Engineer <http://wso2.com/> > WSO2, Inc.:http://wso2.com > > Blog: http://sinthu-rajan.blogspot.com/ > Mobile: +94774273955 > > > -- *Anjana Fernando* Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
