hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8684) Table Coprocessor can't access external HTable by default
Date Wed, 05 Jun 2013 02:03:20 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675532#comment-13675532
] 

Hadoop QA commented on HBASE-8684:
----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12586232/hbase-8684-trunk-v1.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new or modified
tests.

    {color:green}+1 hadoop1.0{color}.  The patch compiles against the hadoop 1.0 profile.

    {color:green}+1 hadoop2.0{color}.  The patch compiles against the hadoop 2.0 profile.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/5940//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5940//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5940//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5940//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5940//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5940//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5940//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5940//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5940//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/5940//console

This message is automatically generated.
                
> 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: 8684-trunk.txt, hbase-8684-0.94-v0.patch, hbase-8684-0.94-v1.patch,
hbase-8684-0.94-v2.patch, hbase-8684-trunk-v1.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
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

Mime
View raw message