Have a look at OpenTSDB (again!). They put a base time in the key and then
have many columns for samples at offsets from that base.
On Tue, Apr 5, 2011 at 10:30 AM, Miguel Costa wrote:
> My focus here is if I gain anything put the timestamp in the columns
> instead than the row , because I will
, because I will have less rows bua a lot more columns with
timestamps.
Thanks,
Miguel
From: Ted Dunning [mailto:tdunn...@maprtech.com]
Sent: terça-feira, 5 de Abril de 2011 17:02
To: user@hbase.apache.org
Cc: Miguel Costa
Subject: Re: Use
What I usually tell people is that if time is part of your model, then put
it in a key.
J-D
On Tue, Apr 5, 2011 at 2:16 AM, Miguel Costa wrote:
> Hi,
>
>
>
> I want to have my data aggregated by day, so I would like to know wich is
> the best option to query my data. To put The timestamp of the
Using timestamp as key will cause your scan to largely hit one region. That
may not be so good.
If you add something in front of the date, you may be able to spread your
scan over several machines.
On the other hand, your aggregation might be very small. In that case, the
convenience of a time
