[ https://issues.apache.org/jira/browse/HBASE-12993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385835#comment-14385835 ]
Hudson commented on HBASE-12993: -------------------------------- SUCCESS: Integrated in HBase-1.0 #837 (See [https://builds.apache.org/job/HBase-1.0/837/]) HBASE-12993 Use HBase 1.0 interfaces in hbase-thrift (Solomon Duskis) (tedyu: rev 8dab79e6f902f765dab561f218c0590b26463b5b) * hbase-server/src/main/java/org/apache/hadoop/hbase/util/ConnectionCache.java * hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServerRunner.java > Use HBase 1.0 interfaces in hbase-thrift > ---------------------------------------- > > Key: HBASE-12993 > URL: https://issues.apache.org/jira/browse/HBASE-12993 > Project: HBase > Issue Type: Bug > Reporter: Solomon Duskis > Assignee: Solomon Duskis > Fix For: 2.0.0, 1.0.1, 1.1.0 > > Attachments: 12993-1.0.patch, HBASE-12993-1.patch, HBASE-12993.patch > > > hbase-thrift uses HTable and HBaesAdmin. It also uses HTablePool, which is > an outdated concept. > As per [~ndimiduk] on the user group: > {quote} > 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. > {quote} -- This message was sent by Atlassian JIRA (v6.3.4#6332)