Where I work, we deal with loads of telecom data. We dint want to deal with
duplicates after loading;so, we handled versions ourself.
The combination of rowkey, column family and the generated column name(column
name is different for different entries)
and the timestamp we generated from the
Strongly consistent reads/writes: HBase is not an eventually consistent
DataStore. This makes it very suitable for tasks such as high-speed counter
aggregation
http://hbase.apache.org/book/architecture.html
Am I missing something ?
- Sri
From: Ian Varley
clusters. That's where you can't get strong
consistency.
Ian
On Dec 7, 2012, at 1:38 PM, sriraam h eliteram...@yahoo.com wrote:
Strongly consistent reads/writes: HBase is not an eventually consistent
DataStore. This makes it very suitable for tasks such as high-speed counter
aggregation
http
