Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of varun@pinterest.com designates
 209.85.223.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADcMMgFNOCLdO2t_O6X11wUpMFf_kcSNFryYgRSpZb7Hh7djZQ@mail.gmail.com>
References: 
 <CAKxWWm14PC8PUOZ0K8tz5ydjGyQyQ-JEseO2v-sCGyQPK7uOkg@mail.gmail.com>
	<CADcMMgFNOCLdO2t_O6X11wUpMFf_kcSNFryYgRSpZb7Hh7djZQ@mail.gmail.com>
Date: Wed, 15 May 2013 08:00:10 -0700
Message-ID: 
 <CAKxWWm1wV0WOXxzZbkLdMT7st8QHxUxH8Q=YwcfGOPW209LHUA@mail.gmail.com>
Subject: Re: Running prefix scans in hbase
From: Varun Sharma <varun@pinterest.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=089e0111d1de9914bc04dcc3019c

--089e0111d1de9914bc04dcc3019c
Content-Type: text/plain; charset=ISO-8859-1

Not after but only before hitting the prefix - I will check the startRow
stuff - I could not find where the seek happens for that...


On Wed, May 15, 2013 at 7:51 AM, Stack <stack@duboce.net> wrote:

> On Tue, May 14, 2013 at 11:33 PM, Varun Sharma <varun@pinterest.com>
> wrote:
>
> > Hi,
> >
> > I was looking at PrefixFilter but going by the implementation - it looks
> we
> > scan every row until we hit the prefix instead of seeking to the row with
> > the required prefix.
> >
> > I was wondering if there are more efficient alternatives which would do a
> > real seek rather than scanning all rows. Would setting startRow and
> stopRow
> > - effectively seek to startRow and then perform the scan ?
> >
>
> Are you saying the prefix filter keeps reading rows even though it has
> passed out the prefix?   I'd think it would return true out of
>
> http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/PrefixFilter.html#filterAllRemaining()once
> it had gone past rows with the prefix?
>
> St.Ack
>

--089e0111d1de9914bc04dcc3019c--