Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 41E729351 for ; Mon, 18 Jun 2012 16:09:43 +0000 (UTC) Received: (qmail 27040 invoked by uid 500); 18 Jun 2012 16:09:43 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 26970 invoked by uid 500); 18 Jun 2012 16:09:43 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 26846 invoked by uid 99); 18 Jun 2012 16:09:42 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jun 2012 16:09:42 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id B90981427F2 for ; Mon, 18 Jun 2012 16:09:42 +0000 (UTC) Date: Mon, 18 Jun 2012 16:09:42 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: <363283872.25389.1340035782761.JavaMail.jiratomcat@issues-vm> In-Reply-To: <480424601.24596.1340020782642.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HBASE-6229) AM.assign() should not set table state to ENABLED directly. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395991#comment-13395991 ] Hadoop QA commented on HBASE-6229: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12532417/HBASE-6229_trunk.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.client.TestFromClientSide Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2183//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2183//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2183//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2183//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: HBASE-6229_94.patch, HBASE-6229_trunk.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