You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jesse Yates (JIRA)" <ji...@apache.org> on 2013/06/04 04:07:21 UTC
[jira] [Created] (HBASE-8684) Table Coprocessor can't access
external HTable by default
Jesse Yates created HBASE-8684:
----------------------------------
Summary: Table Coprocessor can't access external HTable by default
Key: HBASE-8684
URL: https://issues.apache.org/jira/browse/HBASE-8684
Project: HBase
Issue Type: Bug
Reporter: Jesse Yates
Assignee: Jesse Yates
Fix For: 0.94.9
With the default configuration passed to a RegionCoprocessor environment, you cannot reach an HTable on the same cluster (at least in 0.94 - no verified yet in 0.96/8). The reason is in the usage of CompoundConfiguration (backported to 0.94 in HBASE-8176) when loading a table coprocessor we just do (RegionCoprocessorHost, ln 182):
{code}
Configuration newConf = new Configuration(conf);
// set per-table cfspec properties
{code}
but the conf we pass in a CompoundConfiguration, which means the copy constructor from Configuration doesn't work at all.
So, we really need two things:
1. A test that we can reach another HTable in the same cluster via a coprocessor by default
2. Fixing the configuration creation in RegionCoprocessorHost to support (1)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira