[
https://issues.apache.org/jira/browse/HBASE-9749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798380#comment-13798380
]
Hudson commented on HBASE-9749:
-------------------------------
FAILURE: Integrated in HBase-0.94-security #315 (See
[https://builds.apache.org/job/HBase-0.94-security/315/])
HBASE-9749: Custom threadpool for Coprocessor obtained HTables (jyates: rev
1533185)
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/CoprocessorEnvironment.java
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/HTable.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/coprocessor/CoprocessorHost.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/coprocessor/TestOpenTableInCoprocessor.java
> 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
> Fix For: 0.98.0, 0.96.0, 0.94.13
>
> 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)
