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.