You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Solomon Duskis (JIRA)" <ji...@apache.org> on 2015/02/09 16:54:35 UTC
[jira] [Commented] (HBASE-12993) Use HBase 1.0 interfaces in
hbase-thrift
[ https://issues.apache.org/jira/browse/HBASE-12993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312373#comment-14312373 ]
Solomon Duskis commented on HBASE-12993:
----------------------------------------
hbase-rest and hbase-thrift both share some code that needs to be updated. HBASE-12991 will change the common code. HBASE-12993 will track the changes unique to hbase-thrift.
> 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
>
>
> 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)