What is the issue? Don't get blocked by this, as the bam2 stuff are still under development. We will let you know once it is ready for you to finish off the component.
This has to be done right, and I believe this is not a 2 day job of fixing analytics but 2 weeks job of getting bam working end-end. The billing folks should start once everything is verified to work end-end. On Fri, Jun 8, 2012 at 8:44 AM, Kathiravelu Pradeeban <pradee...@wso2.com>wrote: > Hi, > We are done with the publishing. And for the summarizer side, we have to > use the analyzer framework. The analyzer framework (writing analyzer using > hive) complete scenario is not yet tested and KasunW indicated that it will > be done by this week. Since he foresees some potential issues, he told me > he would let me know how to do this, one the complete cycle of testing is > completed. > > We will commit the changes once this is done. > > Regards, > Pradeeban. > > > On Tue, Jun 5, 2012 at 3:40 PM, Sanjeewa Malalgoda <sanje...@wso2.com>wrote: > >> What we have done is use extended AbstractSummaryGenerator and implement >> its >> methods. Inside them we have used data services to read and write data >> from/to database. >> >> Thanks. >> >> >> On Tue, Jun 5, 2012 at 3:30 PM, Kasun Weranga <kas...@wso2.com> wrote: >> >>> >>> >>> On Tue, Jun 5, 2012 at 2:06 PM, Sanjeewa Malalgoda <sanje...@wso2.com>wrote: >>> >>>> >>>> >>>> On Tue, Jun 5, 2012 at 1:54 PM, Kasun Weranga <kas...@wso2.com> wrote: >>>> >>>>> >>>>> >>>>> On Tue, Jun 5, 2012 at 1:06 PM, Sanjeewa Malalgoda >>>>> <sanje...@wso2.com>wrote: >>>>> >>>>>> +1 for doing this change. Actually we have to change few places. >>>>>> >>>>>> 01. Change *Usage agent's* publisherUtils publish method with new >>>>>> publish method pointing to bam2. >>>>>> 02. Modify *Summery generation* code for summarize hourly, daily, >>>>>> monthly >>>>>> >>>>> >>>>> Are you going to modify the existing summary generation code? I think >>>>> better way is to use analyzer framework provided by BAM2 for doing the >>>>> summarization. >>>>> >>>> +for use analyzer frame work. In earlier case also we used extended bam >>>> core summery generator code. >>>> >>>>> 03. Change* Usage service* data retrieving code to get usage data >>>>>> from cassandra. >>>>>> >>>>> >>>>> since the earlier implantation read data from RDBMS. You might use the >>>>> same implementation(with minimal change) If we use hive queries to read >>>>> data from cassandra, then do the summarization and put the summarized data >>>>> into RDBMS as earlier. >>>>> >>>>> We access them by calling Data service (meteringquery.dbs). So is it >>>> possible to use data services with BAM2. >>>> I guess we cant. In that case we might have to write usage service >>>> code. >>>> Also please note that except initial publishing process, we use data >>>> services for almost all the data base operations in usage. >>>> >>> >>> Have you written your own implementation to summarize the usage data ? >>> If so changing code to retrieve data from Cassandra will be enough. But it >>> doesn't scale. >>> >>> Thanks, >>> KasunW >>> >>> Thanks, >>>>> KasunW. >>>>> >>>>> (Usage ui and throttling manager will use this service) >>>>>> >>>>>> Thanks. >>>>>> >>>>>> On Tue, Jun 5, 2012 at 12:09 PM, Kathiravelu Pradeeban < >>>>>> pradee...@wso2.com> wrote: >>>>>> >>>>>>> Hi, >>>>>>> Currently Stratos usage and summarizer components are using BAM >>>>>>> components. This is to be ported to use the new BAM2 in trunk. >>>>>>> We have started working on this, with PublisherUtils of the usage >>>>>>> bundle, to begin with publishing. >>>>>>> >>>>>>> Thank you. >>>>>>> Regards, >>>>>>> Pradeeban. >>>>>>> >>>>>>> -- >>>>>>> Kathiravelu Pradeeban. >>>>>>> Cloud Technologies Team. >>>>>>> WSO2 Inc. >>>>>>> >>>>>>> Blog: [Llovizna] http://kkpradeeban.blogspot.com/ >>>>>>> M: +94 776 477 976 >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Sanjeewa Malalgoda* >>>>>> mobile : +94 713068779 >>>>>> <http://sanjeewamalalgoda.blogspot.com/>blog >>>>>> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/> >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Sanjeewa Malalgoda* >>>> mobile : +94 713068779 >>>> <http://sanjeewamalalgoda.blogspot.com/>blog >>>> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/> >>>> >>> >>> >>> >>> >> >> >> -- >> *Sanjeewa Malalgoda* >> mobile : +94 713068779 >> <http://sanjeewamalalgoda.blogspot.com/>blog >> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/> >> > > > > -- > Kathiravelu Pradeeban. > Cloud Technologies Team. > WSO2 Inc. > > Blog: [Llovizna] http://kkpradeeban.blogspot.com/ > M: +94 776 477 976 > > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Regards, Tharindu blog: http://mackiemathew.com/ M: +94777759908
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
