I believe HTablePool is completely eclipsed by the modern Connection implementation. We'll need to keep the map of UserName => Connection (or maybe the ConnectionCache handles this?) Probably a single Connection (per user) with a large thread pool will do the trick.
On Fri, Feb 6, 2015 at 7:46 AM, Solomon Duskis <[email protected]> wrote: > I'd like to get the hbase thrift server to use the new client (Table, > RegionLocator...). The ThriftServer uses HTablePool to manage Tables. > Is HTablePool a concept worth updating to the new interfaces in the guise > of TablePool? Should we use a single Table that has an ExecutorService > with a large threadpool? Maybe a Connection implementation that has a pool > of tables? > > -Solomon >
