[
https://issues.apache.org/jira/browse/HBASE-12993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385831#comment-14385831
]
Hudson commented on HBASE-12993:
--------------------------------
SUCCESS: Integrated in HBase-1.1 #337 (See
[https://builds.apache.org/job/HBase-1.1/337/])
HBASE-12993 Use HBase 1.0 interfaces in hbase-thrift (Solomon Duskis) (tedyu:
rev 0f0f3f849334801b1d9da9ba3f54f83d0158dba2)
*
hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServerRunner.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/util/ConnectionCache.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)
