[
https://issues.apache.org/jira/browse/HBASE-8218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629748#comment-13629748
]
cuijianwei commented on HBASE-8218:
-----------------------------------
I add a patch which using HConnection and ThreadPool to create HTable in
AggregationClient. I'am not sure whether it's a reasonable way to alleviate the
problem. Consequently, I only use HConnection and ThreadPool to create HTable
in method {code} public <R, S> R max(final byte[] tableName, final
ColumnInterpreter<R, S> ci, final Scan scan) throws Throwable {code} 。I run
TestAggregationClient.java locally and it passes. I can provide a more
completed patch after understand your feedback.
> pass HTable as a parameter to method of AggregationClient
> ---------------------------------------------------------
>
> Key: HBASE-8218
> URL: https://issues.apache.org/jira/browse/HBASE-8218
> Project: HBase
> Issue Type: Improvement
> Components: Client, Coprocessors
> Affects Versions: 0.94.3
> Reporter: cuijianwei
> Attachments: HBASE-8218-0.94.3-v1.txt
>
>
> In AggregationClient, methods such as max(...), min(...) pass 'tableName' as
> a parameter, then a HTable will be created in the method, before the method
> return, the created HTable will be closed.
> The process above may be heavy because each call must create and close a
> HTable. The situation becomes worse when there is only one thread access
> HBase using AggregationClient. The underly HConnection of created HTable will
> also be created and then closed each time when we invoke these method because
> no other HTables using the HConnection. This operation is heavy. Therefore,
> can we add another group of methods which pass HTable or HTablePool as a
> parameter to methods defined in AggregationClient?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
