[
https://issues.apache.org/jira/browse/HBASE-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156449#comment-13156449
]
Lars Hofhansl edited comment on HBASE-4787 at 11/24/11 1:39 AM:
----------------------------------------------------------------
@Nicolas: Correct. It also add the ability to create "unmanaged" HConnections.
This allows for a philosophical change of managing HConnections rather than
HTables. Together with HBASE-3767 that obviates (for us at least) the need for
HTablePool; HTable objects can be created whenever needed. I think that is a
better way of looking at the client, especially in a AppServer setting.
was (Author: lhofhansl):
@Nicolas: Correct. It also add the ability to create "unmanaged"
HConnections.
This allows for a philosophical change of managing HConnections rather than
HTables. Together with HBASE-3767 that obviates (for us at least) the need of
HTablePool, HTable objects can be created whenever needed. I think that is a
better way of looking at the client, especially in a AppServer setting.
> Make corePool as a configurable parameter in HTable
> ---------------------------------------------------
>
> Key: HBASE-4787
> URL: https://issues.apache.org/jira/browse/HBASE-4787
> Project: HBase
> Issue Type: Improvement
> Reporter: Nicolas Spiegelberg
> Priority: Trivial
> Fix For: 0.94.0
>
> Attachments: HBASE-4787.patch
>
>
> Make the corePool a configurable parameter in HTable. So we can tune this
> parameter in the config file. While at it, change the core pool name so we
> can distinguish it from other AppServer pools.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
