[
https://issues.apache.org/jira/browse/HBASE-9117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932537#comment-13932537
]
stack commented on HBASE-9117:
------------------------------
bq. Further, if we introduce the new API as we've discussed with Enis Soztutar,
1.0 will ship with no fewer than 5 ways to acquire a handle on a cluster table
... Surely we can drop something. The pool and the factory are my preference.
You have a point (smile). HTablePool has been deprecated with a while now,
https://github.com/apache/hbase/commit/e4c01dac6bb9cb06a4319a5b2328163911f3aef4,
since 0.96 by my reading so it should be safe to drop.
> 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.2#6252)
