Hi,
On the opentsdb website [1] you can read the following:
---
The problem with HBase's implementation is that every single cell also stores
the row key and a bunch of other redundant information. In the example above
with 2 rows and 16 cells, the 13-byte row key is stored 16 times both on
Yes, the row key is stored with every column.
Avoid ridiculously long row keys :-) Use compression.
On Thu, Apr 14, 2011 at 1:54 PM, Yves Langisch y...@langisch.ch wrote:
Hi,
On the opentsdb website [1] you can read the following:
---
The problem with HBase's implementation is that every
On 14/Apr/2011 13:55, Ryan Rawson wrote:
Yes, the row key is stored with every column.
Avoid ridiculously long row keys :-) Use compression.
So how long is ridiculously long ? 10 bytes? 100? 1000? 10**N ?
On Thu, Apr 14, 2011 at 1:54 PM, Yves Langischy...@langisch.ch wrote:
Hi,
On
Good question, I'd try to keep most row keys 30 bytes, and
definitely avoid 1000 bytes.
On Thu, Apr 14, 2011 at 2:22 PM, David Schnepper dave...@yahoo-inc.com wrote:
On 14/Apr/2011 13:55, Ryan Rawson wrote:
Yes, the row key is stored with every column.
Avoid ridiculously long row keys :-)
