Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7122717D47 for ; Sun, 29 Mar 2015 13:48:53 +0000 (UTC) Received: (qmail 81875 invoked by uid 500); 29 Mar 2015 13:48:53 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 81819 invoked by uid 500); 29 Mar 2015 13:48:53 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 81807 invoked by uid 99); 29 Mar 2015 13:48:53 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Mar 2015 13:48:53 +0000 Date: Sun, 29 Mar 2015 13:48:53 +0000 (UTC) From: "Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-12993) Use HBase 1.0 interfaces in hbase-thrift MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-12993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12993: --------------------------- Attachment: 12993-1.0.patch What got committed to branch-1 and branch-1.0 > 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)