hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Varun Sharma <va...@pinterest.com>
Subject Re: Interactions between max versions and filters
Date Sat, 06 Apr 2013 00:25:57 GMT
HBASE 5257 is probably what lars is talking about - that fixed a bug with
version tracking on ColumnPaginatinoFilter - there is a patch for 0.92,
0.94 and 0.96 but not for the cdh versions...

On Fri, Apr 5, 2013 at 3:28 PM, lars hofhansl <larsh@apache.org> wrote:

> Normally Filters are evaluated before the version counting. There was some
> issue that was fixed recently that changed this behavior specifically for
> ColumnPaginationFilters and friend... Lemme see if I can find that.
>
>
>
> ________________________________
>  From: Stack <stack@duboce.net>
> To: Hbase-User <user@hbase.apache.org>
> Sent: Friday, April 5, 2013 3:05 PM
> Subject: Re: Interactions between max versions and filters
>
> On Fri, Apr 5, 2013 at 11:19 AM, Christophe Taton <taton@wibidata.com
> >wrote:
>
> > Hi,
> >
> > Is there an explicit specification of the behavior of max versions (set
> in
> > a get/scan) when combined with filters?
> > From my experiments (with 0.92 CDH4.1.2), the max versions is applied in
> a
> > way that is neither pre-filtering nor post-filtering.
> > In particular, I am currently playing with the ColumnPaginationFilter,
> and
> > I am not entirely certain I understand the intended/expected behavior.
> > I also did not find an explicit specification in the reference user guide
> > nor in the API javadoc.
> >
>
>
> Hey Christophe:
>
> Sounds like a bug.  My understanding is that the regardless of filters, max
> versions should be respected (Yes, we should have a specification but we do
> not have one here).
>
> Yours,
> St.Ack
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message