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 55BB6100E1 for ; Sat, 15 Mar 2014 15:23:48 +0000 (UTC) Received: (qmail 77659 invoked by uid 500); 15 Mar 2014 15:23:46 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 77314 invoked by uid 500); 15 Mar 2014 15:23:45 -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 77106 invoked by uid 99); 15 Mar 2014 15:23:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Mar 2014 15:23:45 +0000 Date: Sat, 15 Mar 2014 15:23:45 +0000 (UTC) From: "rajeshbabu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-10533) commands.rb is giving wrong error messages on exceptions 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-10533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13936224#comment-13936224 ] rajeshbabu commented on HBASE-10533: ------------------------------------ bq. Seems good to commit. I too feel the same [~lhofhansl]. The fix will work properly with JRuby version 1.6.8 which we are giving in our releases. With other versions of JRuby the first part of fix may not work(HBASE-9211). Not even this hbase shell starting if self fail with JRuby 1.7.0. {code} 2014-02-18 12:43:02,544 INFO [main] Configuration.deprecation: hadoop.native.lib is deprecated. Instead, use io.native.lib.available NoMethodError: undefined method `getTerminal' for Java::Jline::Terminal:Module refresh_width at /home/rajeshbabu/98/hbase-0.98.0/bin/../lib/ruby/shell/formatter.rb:33 initialize at /home/rajeshbabu/98/hbase-0.98.0/bin/../lib/ruby/shell/formatter.rb:46 (root) at /home/rajeshbabu/98/hbase-0.98.0/bin/../bin/hirb.rb:110 {code} ping [~saint.ack@gmail.com],[~jdcryans],[~matteobanerjee] Is it ok to commit or do we need to handle issues with other JRuby versions? > commands.rb is giving wrong error messages on exceptions > -------------------------------------------------------- > > Key: HBASE-10533 > URL: https://issues.apache.org/jira/browse/HBASE-10533 > Project: HBase > Issue Type: Bug > Components: shell > Reporter: rajeshbabu > Assignee: rajeshbabu > Fix For: 0.96.2, 0.99.0, 0.94.19, 0.98.2 > > Attachments: HBASE-10533_trunk.patch > > > 1) Clone into existing table name is printing snapshot name instead of table name. > {code} > hbase(main):004:0> clone_snapshot 'myTableSnapshot-122112','table' > ERROR: Table already exists: myTableSnapshot-122112! > {code} > The reason for this is we are printing first argument instead of exception message. > {code} > if cause.kind_of?(org.apache.hadoop.hbase.TableExistsException) then > raise "Table already exists: #{args.first}!" > end > {code} > 2) If we give wrong column family in put or delete. Expectation is to print actual column families in the table but instead throwing the exception. > {code} > hbase(main):002:0> put 't1','r','unkwown_cf','value' > 2014-02-14 15:51:10,037 WARN [main] util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable > 2014-02-14 15:51:10,640 INFO [main] hdfs.PeerCache: SocketCache disabled. > ERROR: Failed 1 action: org.apache.hadoop.hbase.regionserver.NoSuchColumnFamilyException: Column family unkwown_cf does not exist in region t1,eeeeeeee,1392118273512.c7230b923c58f1af406a6d84930e40c1. in table 't1', {NAME => 'f1', DATA_BLOCK_ENCODING => 'NONE', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0', COMPRESSION => 'NONE', VERSIONS => '6', TTL => '2147483647', MIN_VERSIONS => '0', KEEP_DELETED_CELLS => 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false', BLOCKCACHE => 'true'} > at org.apache.hadoop.hbase.regionserver.HRegionServer.doBatchOp(HRegionServer.java:4206) > at org.apache.hadoop.hbase.regionserver.HRegionServer.doNonAtomicRegionMutation(HRegionServer.java:3441) > at org.apache.hadoop.hbase.regionserver.HRegionServer.multi(HRegionServer.java:3345) > at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:28460) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2008) > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:92) > at org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.consumerLoop(SimpleRpcScheduler.java:160) > at org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.access$000(SimpleRpcScheduler.java:38) > at org.apache.hadoop.hbase.ipc.SimpleRpcScheduler$1.run(SimpleRpcScheduler.java:110) > at java.lang.Thread.run(Thread.java:662) > : 1 time, > {code} > The reason for this is server will not throw NoSuchColumnFamilyException directly, instead RetriesExhaustedWithDetailsException will be thrown. -- This message was sent by Atlassian JIRA (v6.2#6252)