Hi Inosh, IMO the index properties should ideally be defined at the time of the column family creation itself, and as the column family creation takes place based on the stream definition is it not logical to have the index properties there?
@Gayan yes, we will no longer be shipping the current bamdashboard from next release onwards. Thanks, On 7 August 2013 12:22, Gayan Dhanushka <[email protected]> wrote: > Hi Inosh & BAM team, > > With the BAM , UES integration in the picture are we going to continue > supporting the BAM dashboards as it was done earlier or are we going to > encourage creating dashboards using UES? > > +1 for using the latter for dashboards. > > Thanks. > Gayan > > > > > On Wed, Aug 7, 2013 at 12:07 PM, Gihan Anuruddha <[email protected]> wrote: > >> Hi Inosh, >> >> There can be a situation that we might need to use secondary indexes >> without any toolboxes. How we define secondary indexes in such a situation >> ? >> >> Regards, >> Gihan >> >> >> On Tue, Aug 6, 2013 at 7:27 PM, Inosh Goonewardena <[email protected]>wrote: >> >>> Hi, >>> >>> I am working on implementing BAM events & activity search feature. To >>> support the search we need to index some predefined stream properties. We >>> can either use cassandra secondary indexes or we can use our own custom >>> indexes(secondary indexes are not recommended for columns having high >>> cardinality values). Anyway we need to defined the index properties >>> somehow, so we thought of define those in BAM toolbox. >>> >>> In BAM toolbox there is already a configuration file named >>> 'streams.properties'. >>> .tbox >>> |-- analytics <folder> >>> . >>> . >>> |-- dashboard <folder> >>> . >>> . >>> |-- streamDefn <folder> >>> |-- defn_1 <file> >>> |-- defn_2 <file> >>> |-- *streams.properties <file>* >>> >>> 'streams.properties' file is currently use to keep meta information >>> about stream definitions. So I thought of adding two new properties to >>> 'stream.properties' to keep indexing information like belows. >>> >>> * >>> streams.definitions.defn1.secondary.indexes=meta_host,payload_service_name,payload_operation_name >>> streams.definitions.defn1.custom.indexes=correlation_bam_activity_id* >>> >>> WDYT??? >>> >>> -- >>> Regards, >>> >>> Inosh Goonewardena >>> Associate Technical Lead- WSO2 Inc. >>> Mobile: +94779966317 >>> >> >> >> >> -- >> --- >> W.G. Gihan Anuruddha >> Senior Software Engineer | WSO2, Inc. >> M: +94772272595 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > Gayan Dhanushka > Software Engineer > WSO2 Inc. > http://wso2.com > > Mobile : 0716662327 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Balakrishnan Gokulakrishnan* Software Engineer, WSO2, Inc.; http://wso2.com Twitter: http://twitter.com/gokulbs Mobile: +94775935789
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
