[
https://issues.apache.org/jira/browse/HBASE-9117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912184#comment-13912184
]
Enis Soztutar commented on HBASE-9117:
--------------------------------------
bq. Only question is what do we break when this goes in and when should it go
in? For 1.0? Or post 1.0? We are removing deprecated public methods and we are
rationalizing our 'awkward' API so all should be good right?
Some of them have only been deprecated in 0.99, not in 0.98 though.
I am a +1 for doing this, but if there is a way to keep BC by implementing
connection as a different layer so that we don't break clients relying on this
that would be good.
> 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: Nick Dimiduk
> Priority: Critical
> Fix For: 0.99.0
>
> Attachments: HBASE-9117.00.patch, HBASE-9117.01.patch,
> HBASE-9117.02.patch, HBASE-9117.03.patch, HBASE-9117.04.patch,
> HBASE-9117.05.patch, HBASE-9117.06.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.5#6160)
