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 0464EDF92 for ; Thu, 2 Aug 2012 21:31:03 +0000 (UTC) Received: (qmail 59618 invoked by uid 500); 2 Aug 2012 21:31:02 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 59589 invoked by uid 500); 2 Aug 2012 21:31:02 -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 59580 invoked by uid 99); 2 Aug 2012 21:31:02 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Aug 2012 21:31:02 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 992DE142823 for ; Thu, 2 Aug 2012 21:31:02 +0000 (UTC) Date: Thu, 2 Aug 2012 21:31:02 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: <2005997073.7417.1343943062629.JavaMail.jiratomcat@issues-vm> In-Reply-To: <387415616.6912.1343935202653.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HBASE-6503) HBase Shell Documentation For DROP Is Outdated 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-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427635#comment-13427635 ] Hadoop QA commented on HBASE-6503: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12538942/HBASE-6503-example.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 generated 5 javac compiler warnings (more than the trunk's current 4 warnings). -1 findbugs. The patch appears to introduce 10 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 passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2488//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2488//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2488//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2488//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2488//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2488//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2488//console This message is automatically generated. > HBase Shell Documentation For DROP Is Outdated > ---------------------------------------------- > > Key: HBASE-6503 > URL: https://issues.apache.org/jira/browse/HBASE-6503 > Project: HBase > Issue Type: Bug > Reporter: Paul Cavallaro > Assignee: Paul Cavallaro > Priority: Trivial > Attachments: HBASE-6503-example.patch, HBASE-6503.patch > > > HBase Shell help documentation for the drop command says: > "If table has more than one region, run a major compaction on .META." > According to JD this is old news: > jdcryans: back in the days when hadoop didn't support durability it was possible to lose .META. data so we were force flushing .META. and major compacting it all the time also we used to have consistency issues that major compacting was solving ahhh the good old days -- 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