If we store event definitions in mongoDB or HBase, will this work? I believe that is our future todos, so we shouldn't get bound to Cassandra specific ways of doing it...
On Wed, May 1, 2013 at 3:19 PM, Kasun Weranga <[email protected]> wrote: > Since we create CF using the stream definition, If we send these > information with stream definition we can specify indexing columns at the > column family creation time. Also IMO it is easy for users to define the > indexing columns via stream definition. > > > On Tue, Apr 30, 2013 at 9:08 AM, Srinath Perera <[email protected]> wrote: > >> Should this be part of the language? May be we should do this via >> a separate service call instead if putting it inside event definitions. >> >> >> On Mon, Apr 29, 2013 at 7:26 PM, Kasun Weranga <[email protected]> wrote: >> >>> We are planing to do this in BAM 2.5.0. Still we didn't implement it. >>> >>> >>> On Mon, Apr 29, 2013 at 7:17 PM, Srinath Perera <[email protected]>wrote: >>> >>>> Was this done? how was this done? >>>> >>>> >>>> On Fri, Mar 8, 2013 at 5:17 AM, Senaka Fernando <[email protected]>wrote: >>>> >>>>> Hi Kasun, >>>>> >>>>> A good way to help an API to expand is to support a standard format >>>>> and include a standard extension point such that implementation-specifics >>>>> could be included in there. While what you've done is nearly similar, so >>>>> if >>>>> possible please pay attention into this aspect too. >>>>> >>>>> Thanks, >>>>> Senaka. >>>>> >>>>> On Thu, Mar 7, 2013 at 3:38 PM, Kasun Weranga <[email protected]> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> In the current stream definition implementation there is no way to >>>>>> specify event store specific parameters via stream definition. Main >>>>>> use-case for this requirement is to support built-in secondary indexes >>>>>> for >>>>>> events stored in the Cassandra column family. This allows users to define >>>>>> indexing columns for Cassandra column family in the stream definition. So >>>>>> we can define those indexes when we first create the column family using >>>>>> stream definition. >>>>>> >>>>>> We can achieve this by using following format in the stream >>>>>> definition. >>>>>> >>>>>> { >>>>>> 'name':'org.wso2.bam.phone.retail.store.kpi', >>>>>> 'version':'1.0.0', >>>>>> 'nickName': 'Phone_Retail_Shop', >>>>>> 'description': 'Phone Sales', >>>>>> 'eventStoreSpecificParameters' :[ >>>>>> {'indexes':'payload_user,payload_brand'} ], >>>>>> 'metaData':[ >>>>>> {'name':'clientType','type':'STRING'} >>>>>> ], >>>>>> 'payloadData':[ >>>>>> {'name':'brand','type':'STRING'}, >>>>>> {'name':'quantity','type':'INT'}, >>>>>> {'name':'total','type':'INT'}, >>>>>> {'name':'user','type':'STRING'} >>>>>> ] >>>>>> } >>>>>> >>>>>> >>>>>> In the eventStoreSpecificParameters we can define the parameters >>>>>> which are specific for that particular event store, so relevant event >>>>>> persistence implementation can use these parameters to achieve the >>>>>> required >>>>>> functionalities. Also we can make this as and optional parameter, so >>>>>> everyone don't need to define this. >>>>>> >>>>>> Since we are planing to support different event stores in future, I >>>>>> hope this will be useful feature for other event stores too. >>>>>> >>>>>> Suggestions and comments are welcome. >>>>>> >>>>>> Thanks, >>>>>> KasunW. >>>>>> >>>>>> -- >>>>>> *Kasun Weranga* >>>>>> ** >>>>>> Member, Management Committee - Data Technologies >>>>>> Software Engineer >>>>>> *WSO2, Inc. >>>>>> *lean.enterprise.middleware. >>>>>> mobile : +94 772314602 >>>>>> <http://sanjeewamalalgoda.blogspot.com/>blog : >>>>>> http://kasunweranga.blogspot.com/ >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> * <http://wso2con.com/> >>>>> * >>>>> * >>>>> >>>>> Senaka Fernando* >>>>> Member - Integration Technologies Management Committee; >>>>> Technical Lead; WSO2 Inc.; http://wso2.com* >>>>> Member; Apache Software Foundation; http://apache.org >>>>> >>>>> E-mail: senaka AT wso2.com >>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>>> Linked-In: http://linkedin.com/in/senakafernando >>>>> >>>>> *Lean . Enterprise . Middleware >>>>> >>>> >>>> >>>> >>>> -- >>>> ============================ >>>> Srinath Perera, Ph.D. >>>> Senior Software Architect, 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 >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> *Kasun Weranga* >>> ** >>> Member, Management Committee - Data Technologies >>> Software Engineer >>> *WSO2, Inc. >>> *lean.enterprise.middleware. >>> mobile : +94 772314602 >>> <http://sanjeewamalalgoda.blogspot.com/>blog : >>> http://kasunweranga.blogspot.com/ >>> >> >> >> >> -- >> ============================ >> Srinath Perera, Ph.D. >> http://www.cs.indiana.edu/~hperera/ >> http://srinathsview.blogspot.com/ >> > > > > -- > *Kasun Weranga* > ** > Member, Management Committee - Data Technologies > Software Engineer > *WSO2, Inc. > *lean.enterprise.middleware. > mobile : +94 772314602 > <http://sanjeewamalalgoda.blogspot.com/>blog : > http://kasunweranga.blogspot.com/ > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Regards, Tharindu Mathew Associate Technical Lead, WSO2 BAM Member - Data Mgmt. Committee blog: http://tharindumathew.com/ M: +94777759908
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
