Thank you Harsh. You answered my question. I like the current architecture of HBase, which is designed for extensibility for the future -- we have two layer index of data structure, and we can utilize it when needed for specific problems. It looks like you buy a 4 bed-room house, but only utilizing one room for living before having more children. :-)
regards, Lin On Fri, Aug 24, 2012 at 12:46 AM, Harsh J <ha...@cloudera.com> wrote: > Lin, > > On Thu, Aug 23, 2012 at 10:10 PM, Lin Ma <lin...@gmail.com> wrote: > > Thanks, Harsh! > > > > - "HBase currently keeps a single META region (Doesn't split it). " -- > does > > it mean there is only one row in ROOT table, which points the only one > META > > region? > > Yes, currently this is the case. We disabled multiple META regions at > some point, I am unsure about why exactly but perhaps it was complex > to maintain that. > > > - In Big Table, it seems they have multiple META regions (tablets), is > it an > > advantage over HBase? :-) > > Well, depends. A single META region hasn't proven as a scalability > bottleneck to anyone yet. A single META region can easily serve > millions of rows if needed, like any other region, and I've usually > not seen META table grow so big in deployments. > > -- > Harsh J >
