hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Yates (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-8684) Table Coprocessor can't access external HTable by default
Date Tue, 04 Jun 2013 02:11:20 GMT

     [ https://issues.apache.org/jira/browse/HBASE-8684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jesse Yates updated HBASE-8684:

    Attachment: hbase-8684-0.94-v0.patch

Attaching patch with the test for CP table access and fixing the configuration creation by
adding CompoundConfiguration#deepCopy to get the same functional behavior as the original

Should probably add a test for deepCopy, but I'll do that if people are +1 on the rest.
> 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
>         Attachments: hbase-8684-0.94-v0.patch
> 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
>  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

View raw message