[
https://issues.apache.org/jira/browse/HBASE-9117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191398#comment-14191398
]
stack commented on HBASE-9117:
------------------------------
Going through the patch, there is no CatalogTracker nor MetaReader any more.
The 'managed' connections are still possible if you go by deprecated HTable
constructors but we want to keep those for 1.0 (don't want to break folks
rolling upgrade).
bq. [Dropping t]he pool and the factory are my preference.
Pool was smartly moved out and over to thrfit2, the only package that needed
it. HTableFactory is deprecated. Doesn't use pool anymore anyways.
#2 and #3 in your list are done (for 0.99). We won't do #6 and #7 for 0.99.
#1 is a nice-to-have. Should I do it?
Will I start in on #4 and #5?
> 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.2
>
> 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.3.4#6332)
