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

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Incomplete
• Affects Version/s: 0.94.13, 2.0.0
• Component/s: Client, Coprocessors
• Labels: aggregate client coprocessors hbase
• Assignee: Unassigned
• Reporter: Anil Gupta
• Created: 17/Nov/13 03:04
• Updated: 16/Jun/22 18:34
• Resolved: 16/Jun/22 18:34

Description

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.