Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D9E8CF31E for ; Thu, 28 Mar 2013 15:18:30 +0000 (UTC) Received: (qmail 53810 invoked by uid 500); 28 Mar 2013 15:18:28 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 53406 invoked by uid 500); 28 Mar 2013 15:18:26 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 53108 invoked by uid 99); 28 Mar 2013 15:18:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Mar 2013 15:18:24 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mohitanchlia@gmail.com designates 209.85.210.182 as permitted sender) Received: from [209.85.210.182] (HELO mail-ia0-f182.google.com) (209.85.210.182) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Mar 2013 15:18:19 +0000 Received: by mail-ia0-f182.google.com with SMTP id u8so8320985iag.41 for ; Thu, 28 Mar 2013 08:17:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=As6gtl5BUDoVJJMnQ6kX5EcPeHRdZVWdSgbeZrbWpmE=; b=F3LV3mUl8Mn0ZULK4WT+L6WYy1lTr5T1z+XL9xjRxoR5goAPM+1b9XVk/8YFqdK1vk ko9YgGDjDeZUH5rTSj1jgrPWcD/7sM1T7BmLwOigTY8HtLxx2hXJDw0yppwVQqni3twz RJnCobQyFk7oQyqaO5U8MNbwKUpoaceLtltkfSO5b8gxsTcGMBz3+6uOI+CL0k8jO/28 IfgqJagvU3uU444m8DWJVkpiSVIYkJy1/7rJLC70QNkhSIfvGoszQjw68/cPffNUDBl+ fcSn2ctKPWRuLIrgmbuQ2p26mVAZR9tGWmw4PC5YL8mRraF/O1qxtBsImKW5jbk8gV/U dmDA== MIME-Version: 1.0 X-Received: by 10.50.17.131 with SMTP id o3mr7614125igd.112.1364483879054; Thu, 28 Mar 2013 08:17:59 -0700 (PDT) Received: by 10.64.163.6 with HTTP; Thu, 28 Mar 2013 08:17:58 -0700 (PDT) In-Reply-To: References: Date: Thu, 28 Mar 2013 08:17:58 -0700 Message-ID: Subject: Re: Understanding scan behaviour From: Mohit Anchlia To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=14dae934049fe9b45d04d8fda822 X-Virus-Checked: Checked by ClamAV on apache.org --14dae934049fe9b45d04d8fda822 Content-Type: text/plain; charset=ISO-8859-1 My understanding is that the row key would start with +++++ for instance. On Thu, Mar 28, 2013 at 7:53 AM, Jean-Marc Spaggiari < jean-marc@spaggiari.org> wrote: > Hi Mohit, > > I see nothing wrong with the results below. What would I have expected? > > JM > > 2013/3/28 Mohit Anchlia : > > I am running 92.1 version and this is what happens. > > > > > > hbase(main):003:0> scan 'SESSIONID_TIMELINE', {LIMIT => 1, STARTROW => > > 'sdw0'} > > ROW COLUMN+CELL > > s\xC1\xEAR\xDF\xEA&\x89\x91\xFF\x1A^\xB6d\xF0\xEC\x > > column=SID_T_MTX:\x00\x00Rc, timestamp=1363056261106, > > value=PAGE\x09\x091363056252990\x09\x09/ > > 7F\xFF\xFE\xC2\xA3\x84Z\x7F > > > > 1 row(s) in 0.0450 seconds > > hbase(main):004:0> scan 'SESSIONID_TIMELINE', {LIMIT => 1, STARTROW => > > '------'} > > ROW COLUMN+CELL > > -\xA1\xAF>r\xBD\xE2L\x00\xCD*\xD7\xE8\xD6\x1Dk\x7F\ > > column=SID_T_MTX:\x00\x00hF, timestamp=1363384706714, > > value=PAGE\x09239923973\x091363384698919\x09/ > > xFF\xFE\xC2\x8F\xF0\xC1\xBF > > row(s) in 0.0500 seconds > > hbase(main):005:0> scan 'SESSIONID_TIMELINE', {LIMIT => 1, STARTROW => > > '++++'} > > ROW COLUMN+CELL > > +9hC\xFC\x82s\xABL3\xB3B\xC0\xF9\x87\x03\x7F\xFF\xF > > column=SID_T_MTX:\x00\x00<2, timestamp=1364404155426, > > value=PAGE\x09\x091364404145275\x09 \x09/ > > E\xC2S-\x08\x1F > > 1 row(s) in 0.0640 seconds > > hbase(main):006:0> > > > > > > On Wed, Mar 27, 2013 at 9:23 PM, ramkrishna vasudevan < > > ramkrishna.s.vasudevan@gmail.com> wrote: > > > >> Same question, same time :) > >> > >> Regards > >> Ram > >> > >> On Thu, Mar 28, 2013 at 9:53 AM, ramkrishna vasudevan < > >> ramkrishna.s.vasudevan@gmail.com> wrote: > >> > >> > Could you give us some more insights on this? > >> > So you mean when you set the row key as 'azzzaaa', though this row > does > >> > not exist, the scanner returns some other row? Or it is giving you a > row > >> > that does not exist? > >> > > >> > Or you mean it is doing a full table scan? > >> > > >> > Which version of HBase and what type of filters are you using? > >> > Regards > >> > Ram > >> > > >> > > >> > On Thu, Mar 28, 2013 at 9:45 AM, Mohit Anchlia < > mohitanchlia@gmail.com > >> >wrote: > >> > > >> >> I have key in the form of "hashedid + timestamp" but when I run scan > I > >> get > >> >> rows for almost every value. For instance if I run scan for 'azzzaaa' > >> that > >> >> doesn't even exist even then I get the results. > >> >> > >> >> Could someone help me understand what might be going on here? > >> >> > >> > > >> > > >> > --14dae934049fe9b45d04d8fda822--