It seems there are some assumptions in the code that .META. table only has one 
region FIRST_META_REGIONINFO in the following areas:

1) .META. table update with user region info.
2) .META. regions assignment.
3) .META. table split handling.

HBase architecture allows for more than one region in .META. table. I wonder if 
such assumption in the code is just due to the fact that hbase currently 
doesn't don't support large number of regions yet; or there are other reasons 
behind it.

Thanks.

Ming

Reply via email to