On Tue, Nov 9, 2010 at 8:14 AM, Michael Segel <[email protected]> wrote: > The use case for the HTablePool is pretty much the same as any application > where you need to fetch a resource from a pool rather than constantly > instantiate them. > > Really the driving factor on which to use (HTable or HTablePool) is going to > be your use case, or rather what it is you hope to achieve.
HTable isn't thread-safe when you write to HBase. I think that's why HTablePool exists. If you want a highly scalable HBase client in which you don't need to think about pools or thread safety, you can take a look at asynchbase: http://github.com/stumbleupon/asynchbase -- Benoit "tsuna" Sigoure Software Engineer @ www.StumbleUpon.com
