ryano...@gmail.com]
Sent: Monday, May 10, 2010 3:40 AM
To: hbase-user@hadoop.apache.org
Subject: Re: working with versions
The way incrementColumnValue plays with versions is not super clean -
it needs to create new versions at times that are due to technical
necessity not due to business logic.
The way incrementColumnValue plays with versions is not super clean -
it needs to create new versions at times that are due to technical
necessity not due to business logic.
At SU we have a data scheme where we put the date in the key and then
use incrementColumnValue to keep the column data part
There is a method on the table to increment values:
someHBaseTable.incrementColumnValue()
Look it up in the javadocs.
On Sun, May 9, 2010 at 10:03 AM, Lior Schachter wrote:
> Hi,
>
> Suppose I want to keep aggregated data (e.g. counters) per day for a year
> or
> so (this way I can query hbase
Hi,
Suppose I want to keep aggregated data (e.g. counters) per day for a year or
so (this way I can query hbase on a specific date range).
Is the proper way to do this is to use the in-built versions mechanism of a
column i.e. open a new version every day and then when query - sum the right
versi
