Hi Asanka, As in BAM 241, Cassandra indexing will affect only for the data which receive after adding the index, and there is no mechanism to index the already existing data. If this implemented, we have to handle the size of already existing data, and the load it will create, and the time it will take to complete the process. I believe, it will be better if this can be added to BAM road map with a proper solution to all the upcoming problems.
Thanks, Pandula On Fri, Jul 25, 2014 at 12:49 PM, Asanka Vithanage <asan...@wso2.com> wrote: > Hi All, > > According to the current BAM implementation, We are supporting message > and activity search based on the Cassandra indexing via message console UI. > > Currently to make data indexing work, we have to define indexing on tBox > and deploy it.But even after tBox deployed, indexing won't get executed > till we publish new set of data. > So According to this there is no way to index existing cassandra data set > through BAM. > If its possible how can i achieve that? > > Further since indexing can be considered as separate feature directly bind > with cassandra, I believe we should provide a separate UI to execute > indexing stuffs and It will increase the usability of BAM indexing feature. > WDYT? > > > > > -- > Asanka Vithanage > Senior Software Engineer -QA > Mobile: +94 0716286708 > Email: asan...@wso2.com > WSO2 Inc. www.wso2.com > > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Pandula Kariyawasam K.B.* *Senior Software Engineer - QA* Mobile: +94772314510 <http://www.wso2.com>
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
