[
https://issues.apache.org/jira/browse/HBASE-8218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anoop Sam John updated HBASE-8218:
----------------------------------
Resolution: Fixed
Release Note: In AggregationClient added a new set of APIs which takes an
HTable instance rather than just table name. When client needs to call more
than one aggregation API or they do have an instance of the HTable already
available, they can pass it so as to avoid the overhead of creating the HTable
again and again.
Status: Resolved (was: Patch Available)
Committed to Trunk. Thanks for the reviews
> Pass HTable as parameter to methods 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
> Assignee: Anoop Sam John
> Fix For: 0.98.0
>
> Attachments: 8218-trunk-v2-rerun.txt, 8218-trunk-v2.txt,
> 8218-trunk-v3-rerun.txt, 8218-trunk-v3.txt, HBASE-8218-0.94.3-v1.txt,
> HBASE-8218-0.94.3-v2.txt, HBASE-8218-0.94.3-v3.txt, HBASE-8218-trunk-v1.txt,
> HBase-8218_Trunk_V4.patch, HBase-8218_Trunk_V5.patch
>
>
> 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 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
