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 EAB90F1C9 for ; Mon, 8 Apr 2013 18:37:33 +0000 (UTC) Received: (qmail 67539 invoked by uid 500); 8 Apr 2013 18:37:31 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 67490 invoked by uid 500); 8 Apr 2013 18:37:31 -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 67482 invoked by uid 99); 8 Apr 2013 18:37:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Apr 2013 18:37:31 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.212.44] (HELO mail-vb0-f44.google.com) (209.85.212.44) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Apr 2013 18:37:27 +0000 Received: by mail-vb0-f44.google.com with SMTP id e12so4035212vbg.31 for ; Mon, 08 Apr 2013 11:37:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=98FbiSjMWZax12vEAPbcjChw9HbrPh/1YPpiGtrFEWI=; b=G9yQPl2GGokirY5HbPGtLArCmmnFQt4RN5wMW32HeeFftpWSdQzzrl6ZxgryDTNOB6 MA+Pi/nzo0/YjHTQ1YmXcAME/pWLYaRBd3ZzTVLKC2iALuuLzWBOM4znkmsv0OXGg/23 wUkHGxqe0oJHCSxvDFjYQNRkyyfEjxGcjClUVpHIFrRfOh8sOltWoYyGWvwfcWhU3J5k 0qD3A8rfl7tM+lvx4VwEPGm13vr+B7aY3zltZGF5bdbuaoUFJLN3+EFFT3sMGgdytL61 aieSkz99dPwdGCWK36pKFe8x/i1E7KaAoxIKV9FOnewX62m7CdBt7GljfYYUjbDyRM9N 53NQ== X-Received: by 10.52.94.17 with SMTP id cy17mr2502002vdb.68.1365446226406; Mon, 08 Apr 2013 11:37:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.30.20 with HTTP; Mon, 8 Apr 2013 11:36:45 -0700 (PDT) In-Reply-To: References: From: Jean-Marc Spaggiari Date: Mon, 8 Apr 2013 14:36:45 -0400 Message-ID: Subject: Re: Best way to query multiple sets of rows To: user@hbase.apache.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQkNbyWMMVYjVZf811u694QlxTHzANEPCks9bluZJerVbw8qI802Gci/xJl9hU7mo8ylC7kA X-Virus-Checked: Checked by ClamAV on apache.org That's exact. In your situation, you will have to create 3 scans. One with startRow from A and endrow to B One with startRow from C and endrow to D One with startRow from E and endrow to F You can even do then in parallele if you want. JM 2013/4/8 Graeme Wallace : > I thought a Scan could only cope with one start row and an end row ? > > > On Mon, Apr 8, 2013 at 1:27 PM, Jean-Marc Spaggiari > wrote: > >> Hi Greame, >> >> The scans are the right way to do that. >> >> They will give you back all the data you need, chunck by chunk. Then >> yoiu have to iterate over the data to do what you want with it. >> >> What was your expectation? I'm not sure I'm getting your "so that i >> dont have to issue sequential Scans". >> >> jM >> >> 2013/4/8 Graeme Wallace : >> > Hi, >> > >> > Maybe there is an obvious way but i'm not seeing it. >> > >> > I have a need to query HBase for multiple chunks of data, that is >> something >> > equivalent to >> > >> > select columns >> > from table >> > where rowid between A and B >> > or rowid between C and D >> > or rowid between E and F >> > etc. >> > >> > in SQL. >> > >> > Whats the best way to go about doing this so that i dont have to issue >> > sequential Scans ? >> > >> > -- >> > Graeme Wallace >> > CTO >> > FareCompare.com >> > O: 972 588 1414 >> > M: 214 681 9018 >> > > > > -- > Graeme Wallace > CTO > FareCompare.com > O: 972 588 1414 > M: 214 681 9018