Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 8 Nov 2013 16:25:19 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12661440.1375465770546.42923.1383927919858@arcas>
In-Reply-To: <JIRA.12661440.1375465770546@arcas>
References: <JIRA.12661440.1375465770546@arcas>
Subject: [jira] [Commented] (HBASE-9117) Remove HTablePool and all
 HConnection pooling related APIs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-9117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817405#comment-13817405 ] 

stack commented on HBASE-9117:
------------------------------

[~nkeywal] Do the createConnections have a corresponding close?

I suppose this a pretty radical change making it so every time we create a scanner, even if a short scanner, we make a new connection; that is more heavyweight? 

I love the cleanup.

We going to break clients?  I suppose we've deprecated for a long time now AND what we have is really messy to make sense of.

> Remove HTablePool and all HConnection pooling related APIs
> ----------------------------------------------------------
>
>                 Key: HBASE-9117
>                 URL: https://issues.apache.org/jira/browse/HBASE-9117
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>             Fix For: 0.98.0
>
>         Attachments: HBASE-9117.00.patch
>
>
> The recommended way is now:
> # Create an HConnection: HConnectionManager.createConnection(...)
> # Create a light HTable: HConnection.getTable(...)
> # table.close()
> # connection.close()
> All other API and pooling will be removed.


--
This message was sent by Atlassian JIRA
(v6.1#6144)