I think a similar concept would be a great idea. It would definitely
prevent the type of issue that you mentioned. I think that if it was done
in a similar way to how it is handled for hadoop, where you can specify a
list, but if you don't, you get autoadd, should keep everyone happy.
Mike
On Thu, Mar 8, 2012 at 2:52 PM, Stack st...@duboce.net wrote:
On Thu, Mar 8, 2012 at 11:50 AM, de Souza Medeiros Andre
andre.medei...@aalto.fi wrote:
Or does this happen only with one-region tables?
Yes
Even with multiregion tables, you will still get a null start key for the
first
On Thu, Mar 8, 2012 at 2:50 PM, de Souza Medeiros Andre
andre.medei...@aalto.fi wrote:
Thanks for the answer.
This is quite confusing though, what is the point of having a method to
retrieve the last key if we know that anyway it will be an empty byte array?
Or does this happen only with
You really need to consider the entire historical context here. A lot of
the memory used in hbase is buffering writes to disk and for the block
cache. These days, it isn't unreasonable to get 12 2-3TB disks in a
commodity server. Back in 2003, you would not get as many disks, and they
would be
