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 38C10D81F for ; Mon, 22 Oct 2012 19:56:13 +0000 (UTC) Received: (qmail 36315 invoked by uid 500); 22 Oct 2012 19:56:13 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 36257 invoked by uid 500); 22 Oct 2012 19:56:13 -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 36195 invoked by uid 99); 22 Oct 2012 19:56:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Oct 2012 19:56:12 +0000 Date: Mon, 22 Oct 2012 19:56:12 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: <338103702.11986.1350935772925.JavaMail.jiratomcat@arcas> In-Reply-To: <917115055.4237.1345872299777.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (HBASE-6665) ROOT region should not be splitted even with META row as explicit split key 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-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481733#comment-13481733 ] Hadoop QA commented on HBASE-6665: ---------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12550327/HBASE-6665_trunk.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 3 new or modified tests. {color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop 2.0 profile. {color:red}-1 javadoc{color}. The javadoc tool appears to have generated 82 warning messages. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:red}-1 findbugs{color}. The patch appears to introduce 5 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 core tests{color}. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/3112//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3112//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3112//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3112//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3112//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3112//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3112//console This message is automatically generated. > ROOT region should not be splitted even with META row as explicit split key > --------------------------------------------------------------------------- > > Key: HBASE-6665 > URL: https://issues.apache.org/jira/browse/HBASE-6665 > Project: HBase > Issue Type: Bug > Reporter: Y. SREENIVASULU REDDY > Attachments: HBASE-6665_trunk.patch > > > split operation on ROOT table by specifying explicit split key as .META. > closing the ROOT region and taking long time to rollback failed split. > I think we can skip split for ROOT table as how we are doing for META region. -- 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