2 suggestions for discussion: [Key-Schema 1]: Sensor + time(milliseconds) + XXXX + V1V2V3
XXXX :- M bytes random number. V1V2V3 :- Limit the length for each metrics. Likes v1=10, v2=8, v3=9. And the length we set to 3. The value should be : 010008009. [Key-Schema 2]: Sensor + time(milliseconds) + XXXX XXXX :- M bytes random number. Just store the metrics in value part. Jieshan -----Original Message----- From: Rita [mailto:[email protected]] Sent: Thursday, September 20, 2012 8:04 PM To: [email protected] Cc: Zhouxunmiao Subject: Re: time series question Jieshan, v is not a version number. v1, v2, v3 are actually metrics. My data is high frequency therefore in one second I can have several hundred entries in it. Would using nested entity work in such as case? key=sensor+time cf=d cf:d,t1 (v1=0,v2=4,v3=0) cf:d,t2 (v1=0,v2=4,v3=0) cf:d,t2 (v1=0,v2=4,v3=2) But now sure efficient this would be. Also, for creating an entity like this. Would I need to do my own serializing? would JSON work? On Wed, Sep 19, 2012 at 10:37 PM, Bijieshan <[email protected]> wrote: > I prefer the idea similar to " sensor+time+v "...The problem is the part > of "v". Is it the version number? Or some random number to distinguish the > different version? > > Jieshan > -----Original Message----- > From: Rita [mailto:[email protected]] > Sent: Thursday, September 20, 2012 9:09 AM > To: [email protected] > Subject: time series question > > Yet another time series questions. > > I have an issue where my row key will be the same but I will have multiple > versions of the data. I dont need only the last one instead I need all X > number of versions. Here I have 3 different versions. > > sensor,time,v1,v2,v3 > c04,0930001,0,0,0 > c04,0930001,0,4,0 > c04,0930001,0,4,3 > > key=sensor+time > cf=d > cf:v1 > cf:v2 > cf:v3 > > I plan to query, like this. At 093001 was was the v1 of c04? same for v2 > and v3? > > I dont want to use the native Hbase version feature because some sensors > have more than 100 different, ¨ticks¨ and I would like to keep track of all > of them. Perhaps, I should change my key to include sensor+time+v value? > Any thoughts or clever schemas I can use? > > > > > > > -- > --- Get your facts first, then you can distort them as you please.-- > -- --- Get your facts first, then you can distort them as you please.--
