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-6229) AM.assign() should not set table state to ENABLED directly.
Date Wed, 20 Jun 2012 04:39:43 GMT

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

Hadoop QA commented on HBASE-6229:
----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12532639/6229_trunk_2.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    +1 hadoop2.0.  The patch compiles against the hadoop 2.0 profile.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    -1 findbugs.  The patch appears to introduce 7 new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit
warnings.

     -1 core tests.  The patch failed these unit tests:
                       org.apache.hadoop.hbase.util.TestHBaseFsck

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2195//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2195//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2195//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2195//console

This message is automatically generated.
                
> AM.assign() should not set table state to ENABLED directly.
> -----------------------------------------------------------
>
>                 Key: HBASE-6229
>                 URL: https://issues.apache.org/jira/browse/HBASE-6229
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.92.2, 0.94.1
>            Reporter: rajeshbabu
>            Assignee: rajeshbabu
>             Fix For: 0.96.0, 0.94.1, 0.92.3
>
>         Attachments: 6229_trunk_2.patch, HBASE-6229_94.patch, HBASE-6229_94_1.patch,
HBASE-6229_94_2.patch, HBASE-6229_trunk.patch, HBASE-6229_trunk_1.patch
>
>
> In case of assign from EnableTableHandler table state is ENABLING. Any how EnableTableHandler
will set ENABLED after assigning all the the table regions. If we try to set to ENABLED directly
then client api may think ENABLE table is completed. When we have a case like all the regions
are added directly into META and we call assignRegion then we need to make the table ENABLED.
 Hence in such case the table will not be in ENABLING or ENABLED state.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message