Hello,
I got most, but not all, answers about schemas from the HBase Book and
the "Definite Guide".
Let's say there is a single row key and I use this key to add to two
tables, one row each (case (1)).
Could someone please confirm that even though the tables are different,
based on the key, this data will end up in the same or at least adjacent
regions? (I.e. my hbase client has to deal with two HTable instances but
only one region server needs to be looked up)?
Thank you,
Tom
Background:
I have two types of data: meta data (low volume) and measurement data
(high volume); and I get requests coming in where, based on an ID, I
need my HBase client to be able to access both metadata and measurement
data for this ID quickly. I want to reduce communication overhead
(lookups, number of tcp connections etc).
In regards to dealing with the two types of data in Hbase, I see these
three design choices, which one to go for?
(1) Multiple tables - single key - single column family
(2) Single table - single key - multiple column families (the HBase Book
advises against that in section 6.2).
(3) Single table - multiple keys (all made in such a way that they will
be co-located and system wide hot spots are avoided) - single column family
