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 1F52810433 for ; Mon, 11 Nov 2013 13:16:23 +0000 (UTC) Received: (qmail 51416 invoked by uid 500); 11 Nov 2013 13:16:19 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 51370 invoked by uid 500); 11 Nov 2013 13:16:18 -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 51346 invoked by uid 99); 11 Nov 2013 13:16:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Nov 2013 13:16:17 +0000 Date: Mon, 11 Nov 2013 13:16:17 +0000 (UTC) From: "Jean-Marc Spaggiari (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-9942) hbase Scanner specifications accepting wrong specifier and then after scan using correct specifier returning unexpected result 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-9942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818934#comment-13818934 ] Jean-Marc Spaggiari commented on HBASE-9942: -------------------------------------------- Wierd. I just tried wit 0.96.0 and faced the same issue. > hbase Scanner specifications accepting wrong specifier and then after scan using correct specifier returning unexpected result > ------------------------------------------------------------------------------------------------------------------------------- > > Key: HBASE-9942 > URL: https://issues.apache.org/jira/browse/HBASE-9942 > Project: HBase > Issue Type: Bug > Components: Client > Affects Versions: 0.96.0, 0.94.13 > Reporter: Deepak Sharma > Priority: Minor > > check the given scenerio: > 1. log in to hbase client --> ./hbase shell > 2. created table 'tab1' > hbase(main):001:0> create 'tab1' , 'fa1' > 3. put some 10 rows (row1 to row10) in table 'tab1' > 4. run the scan for table 'tab1' as follows: > > hbase(main):013:0> scan 'tab1' , { STARTROW => 'row4' , STOPROW => 'row9' } > ROW COLUMN+CELL > row4 column=fa1:col1, timestamp=1384164182738, value=value1 > row5 column=fa1:col1, timestamp=1384164188396, value=value1 > row6 column=fa1:col1, timestamp=1384164192395, value=value1 > row7 column=fa1:col1, timestamp=1384164197693, value=value1 > row8 column=fa1:col1, timestamp=1384164203237, value=value1 > 5 row(s) in 0.0540 seconds > so result was expected , rows from 'row4' to 'row8' are displayed > 5. then run the scan using wrong specifier ( '=' instead of '=>') so get wrong result > hbase(main):014:0> scan 'tab1' , { STARTROW = 'row4' , STOPROW = 'row9' } > ROW COLUMN+CELL > row1 column=fa1:col1, timestamp=1384164167838, value=value1 > row10 column=fa1:col1, timestamp=1384164212615, value=value1 > row2 column=fa1:col1, timestamp=1384164175337, value=value1 > row3 column=fa1:col1, timestamp=1384164179068, value=value1 > row4 column=fa1:col1, timestamp=1384164182738, value=value1 > row5 column=fa1:col1, timestamp=1384164188396, value=value1 > row6 column=fa1:col1, timestamp=1384164192395, value=value1 > row7 column=fa1:col1, timestamp=1384164197693, value=value1 > row8 column=fa1:col1, timestamp=1384164203237, value=value1 > row9 column=fa1:col1, timestamp=1384164208375, value=value1 > 10 row(s) in 0.0390 seconds > 6. now performed correct scan query with correct specifier ( used '=>' as specifier) > hbase(main):015:0> scan 'tab1' , { STARTROW => 'row4' , STOPROW => 'row9' } > ROW COLUMN+CELL > row1 column=fa1:col1, timestamp=1384164167838, value=value1 > row10 column=fa1:col1, timestamp=1384164212615, value=value1 > row2 column=fa1:col1, timestamp=1384164175337, value=value1 > row3 column=fa1:col1, timestamp=1384164179068, value=value1 > row4 column=fa1:col1, timestamp=1384164182738, value=value1 > row5 column=fa1:col1, timestamp=1384164188396, value=value1 > row6 column=fa1:col1, timestamp=1384164192395, value=value1 > row7 column=fa1:col1, timestamp=1384164197693, value=value1 > row8 column=fa1:col1, timestamp=1384164203237, value=value1 > row9 column=fa1:col1, timestamp=1384164208375, value=value1 > 10 row(s) in 0.0450 seconds > now even if i have passed correct scan query then also i am getting wrong result > Defect: > check in step 6 as per scan query , only row4 to row9 should be displayed but output result is displaying all the rows in this table > Note: when i exit the shell and again loging and perform the same query then result was correct -- This message was sent by Atlassian JIRA (v6.1#6144)