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 B053810C81 for ; Tue, 2 Jul 2013 21:55:20 +0000 (UTC) Received: (qmail 20860 invoked by uid 500); 2 Jul 2013 21:55:20 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 20830 invoked by uid 500); 2 Jul 2013 21:55:20 -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 20821 invoked by uid 99); 2 Jul 2013 21:55:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jul 2013 21:55:20 +0000 Date: Tue, 2 Jul 2013 21:55:20 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8798) Fix a minor bug in shell command with clone_snapshot table error 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-8798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698300#comment-13698300 ] Hadoop QA commented on HBASE-8798: ---------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12590503/8798-v3.txt against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. 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. {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/6195//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6195//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6195//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6195//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6195//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6195//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6195//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6195//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6195//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/6195//console This message is automatically generated. > Fix a minor bug in shell command with clone_snapshot table error > ---------------------------------------------------------------- > > Key: HBASE-8798 > URL: https://issues.apache.org/jira/browse/HBASE-8798 > Project: HBase > Issue Type: Bug > Components: shell, snapshots > Affects Versions: 0.94.8, 0.95.1 > Reporter: Jerry He > Assignee: Ted Yu > Priority: Minor > Attachments: 8798-trunk-v2.txt, 8798-v3.txt, HBASE-8798-trunk.patch > > > In HBase shell, the syntax for clone_snapshot is: > hbase> clone_snapshot 'snapshotName', 'tableName' > If the target table already exists, we'll get an error. > For example: > ------------------ > hbase(main):011:0> clone_snapshot 'mysnapshot1', 'TestTable' > ERROR: Table already exists: mysnapshot1! > Here is some help for this command: > Create a new table by cloning the snapshot content. > There're no copies of data involved. > And writing on the newly created table will not influence the snapshot data. > Examples: > hbase> clone_snapshot 'snapshotName', 'tableName' > ---------------------- > The bug is in the ERROR message: > *ERROR: Table already exists: mysnapshot1!* > We should output the table name, not the snapshot name. > Currently, in command.rb, we have the output fixed as args.first for TableExistsException: > {code} > def translate_hbase_exceptions(*args) > yield > rescue org.apache.hadoop.hbase.exceptions.TableNotFoundException > raise "Unknown table #{args.first}!" > rescue org.apache.hadoop.hbase.exceptions.NoSuchColumnFamilyException > valid_cols = table(args.first).get_all_columns.map { |c| c + '*' } > raise "Unknown column family! Valid column names: #{valid_cols.join(", ")}" > rescue org.apache.hadoop.hbase.exceptions.TableExistsException > raise "Table already exists: #{args.first}!" > end > {code} > This is fine with commands like 'create tableName ...' but not 'clone_snapshot snapshotName tableName'. -- 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