Yes, you will be wasting some IO, this is a well known bug in HBase,
but it's not because empty families would be flushes. In HBase,
usually if something is empty it means it doesn't exist (that's why
sparse columns are free). Now if you insert in 4 families in different
rows but all in the same re
How about Column Families? We have 4 column families per table due to
different settings (versions etc.). They are sparse in that a given row will
only ever write to a single CF and even regions usually have only 1 CF's
data/store file except at the border between row key naming conventions
(each C
Its not the number of tables that is of import, its the number of
regions. You can have your regions in as many tables as you like. I
do not believe there a cost to having more tables.
St.Ack
On Wed, May 18, 2011 at 5:54 AM, Wayne wrote:
> How many tables can a cluster realistically handle or
How many tables can a cluster realistically handle or how many tables/node
can be supported? I am looking for a realistic idea of whether a 10 node
cluster can support 100 or even 500 tables. I realize it is recommended to
have a few tables at most (and to use the row key to add everything to one
t
