[jira] [Commented] (HBASE-9984) AggregationClient creates a new Htable, HConnection,and ExecutorService in every CP call.

["Anoop Sam John (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13825111#comment-13825111 ] 

Anoop Sam John commented on HBASE-9984:
---------------------------------------

I think it is done in 96+ version. Can u pls check once in Trunk?

> AggregationClient creates a new Htable, HConnection,and ExecutorService in every CP call.
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-9984
>                 URL: https://issues.apache.org/jira/browse/HBASE-9984
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client, Coprocessors
>    Affects Versions: 0.94.13
>            Reporter: Anil Gupta
>            Priority: Minor
>              Labels: aggregate, client, coprocessors, hbase
>
> At present AggregationClient takes Conf in constructor and create a new Htable instance on every method calls. The constructor of HTable used in AggregationClient is very heavy as it creates a new HConnection and ExecutorService. 
> Above mechanism is not convenient where the Application is managing HTable, HConnection, ExecutorService by itself. So, i propose 
> 1# AggregationClient should provide an additional constructor: AggregationClient(HTable)
> 2# Provide methods that takes Htable.
> In this way we can avoid creation of Htable, HConnection,and ExecutorService in every CP call. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)