From issues-return-336146-archive-asf-public=cust-asf.ponee.io@hbase.apache.org Fri Mar 2 02:24:06 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 349A118064D for ; Fri, 2 Mar 2018 02:24:06 +0100 (CET) Received: (qmail 14426 invoked by uid 500); 2 Mar 2018 01:24:05 -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 14414 invoked by uid 99); 2 Mar 2018 01:24:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2018 01:24:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 77CF1C0611 for ; Fri, 2 Mar 2018 01:24:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id g69kULxDP5Nd for ; Fri, 2 Mar 2018 01:24:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id EB0745FB02 for ; Fri, 2 Mar 2018 01:24:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7F786E023A for ; Fri, 2 Mar 2018 01:24:02 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 837A82477D for ; Fri, 2 Mar 2018 01:24:00 +0000 (UTC) Date: Fri, 2 Mar 2018 01:24:00 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (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:all-tabpanel ] stack updated HBASE-9942: ------------------------- Fix Version/s: (was: 2.0.0) > 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 (v7.6.3#76005)