[
https://issues.apache.org/jira/browse/HBASE-9749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798192#comment-13798192
]
stack commented on HBASE-9749:
------------------------------
bq. External interface and functionality to users is the same, this way just
minimizes the possible code paths
External Interface is the same? No external code -- cps or whatever -- will
use this method that you are changing? If so, +1 on patch. Otherwise,
consider override to minimize need for users to ch ange their code.
> Custom threadpool for Coprocessor obtained HTables
> --------------------------------------------------
>
> Key: HBASE-9749
> URL: https://issues.apache.org/jira/browse/HBASE-9749
> Project: HBase
> Issue Type: Improvement
> Components: Coprocessors
> Affects Versions: 0.98.0, 0.94.13, 0.96.1
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Attachments: hbase-9749-0.94-v0.patch, hbase-9749-0.96-v0.patch,
> hbase-9749-trunk-v0.patch
>
>
> Coprocessors currently can only use the default HTable constructor that takes
> a single thread-pool.This is overly constrictive for coprocessors that desire
> tighter control over their resources.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
