[
https://issues.apache.org/jira/browse/HBASE-9117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920120#comment-13920120
]
Enis Soztutar commented on HBASE-9117:
--------------------------------------
bq. Here's what I have in mind in terms of breakdown of work.
I think it makes a lot of sense to break it down.
>From your plan, it seems that you are suggesting we get rid of "managed"
>connections from HTable completely. I don't think we can do 4 and 5 in 0.98
>that would be a big change.
I am less in favor of 6 and 7, because it would imply that we break most of the
clients, and the transition period is not enough.
bq. Given that connections will no longer be cached, HConnectionManager is
really only a factory. We should evaluate whether this is necessary in a 1.0
API.
I think it is good to keep it. We can just replace this with HConnection
constructors, but since we already have it, we can keep it as the main factory.
We can also do a clean ConnectionFactory class as well to replace it as a fresh
start.
bq. Should also remove HTablePool as it's own item.
I say deprecate instead of remove in 1.0
> 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)
