Hi, We are using hbase to power a web application. The current implementation of the data access classes maintain a static HTable instance to read and write. The reason being getting hold of HTable instance looks costly.
In this scenario the HTable instances could more or less be perpetually cached. Is it reasonable to assume that HTables do not have some inherent timeout and are threadsafe across gets and puts? Thanks and regards, - Ashish
