[
https://issues.apache.org/jira/browse/HBASE-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174874#comment-13174874
]
Bruno Dumon commented on HBASE-5084:
------------------------------------
(I'm a Lily developer)
The main reason I'm not using that HConnection/ExecutorService constructor is
because we are using CDH's HBase which does not have that HTable constructor
yet.
Otherwise, I like the idea of managing both HConnection and ExecutorService
myself. Though it seems like two different issues. Rather than connection not
being null, you'd need a constructor HTable(Configuration, tableName,
ExecutorService). Not sure if it's worth adding another constructor, you can as
well call HConnectionManager.getConnection().
> Allow different HTable instances to share one ExecutorService
> -------------------------------------------------------------
>
> Key: HBASE-5084
> URL: https://issues.apache.org/jira/browse/HBASE-5084
> Project: HBase
> Issue Type: Task
> Reporter: Zhihong Yu
>
> This came out of Lily 1.1.1 release:
> Use a shared ExecutorService for all HTable instances, leading to better (or
> actual) thread reuse
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
