Hi Sanjeewa,

USAGE_LAST_HOURLY_TS should be created at the time of setting up the
environment. Scripts for all the metering related tables are currently
available under the Stratos Manager product. If the last timestamp is not
present we consider the epoch time [1] as the last timestamp, which is
January 1, 1970.

Toolbox does not need to include the stream definitions AFAIU. We only need
the keyspace and the CF name which we provide in the hive script which is
in the toolbox. Stream definitions is handled by the usage agent code and
CF name depends on the name which is part of the stream def.

Note that we have two toolboxes, one fore usage data and one for service
stats.

Regards,
AmilaM.


[1] http://en.wikipedia.org/wiki/Epoch_%28reference_date%29

On Mon, Mar 25, 2013 at 4:07 PM, Sanjeewa Malalgoda <[email protected]>wrote:

> Hi All,
> I'm having couple of issues after went through summery helper class and
> usage implementation. I wanted to know who creates USAGE_LAST_HOURLY_TS
> table initially. It seems nobody creates it but summery helper is trying to
> use it. Also i think if no data present in USAGE_LAST_HOURLY_TS table we
> should take some random date like 2000-01-01:12:00. Or else we can take 1
> hour before the current time stamp and use it for last summery time(in very
> first time). Where do we keep table schema related to usage data? (Even if
> it create by usage toolbox at run time, we should have schema some where).
> Also i think stream definitions(bandwidth and request related) should be
> included into toolbox as well. WDYT? Please correct me if i understood
> anything in a wrong manner.
>
> Thanks.
> --
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +14084122175 | +94713068779
>
>  <http://sanjeewamalalgoda.blogspot.com/>blog
> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/>
>



-- 
*Amila Maharachchi*
Technical Lead
Member, Management Committee - Cloud & Platform TG
WSO2, Inc.; http://wso2.com

Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to