hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Taylor <jtay...@salesforce.com>
Subject Re: row filter - binary comparator at certain range
Date Mon, 21 Oct 2013 06:05:24 GMT
Take a look at Phoenix(https://github.com/forcedotcom/phoenix). It supports
both salting and fuzzy row filtering through its skip scan.


On Sun, Oct 20, 2013 at 10:42 PM, Premal Shah <premal.j.shah@gmail.com>wrote:

> Have you looked at FuzzyRowFilter? Seems to me that it might satisfy your
> use-case.
>
> http://blog.sematext.com/2012/08/09/consider-using-fuzzyrowfilter-when-in-need-for-secondary-indexes-in-hbase/
>
>
> On Sun, Oct 20, 2013 at 9:31 PM, Tony Duan <duanjianmin@126.com> wrote:
>
> > Alex Vasilenko <aa.vasilenko@...> writes:
> >
> > >
> > > Lars,
> > >
> > > But how it will behave, when I have salt at the beginning of the key to
> > > properly shard table across regions? Imagine row key of format
> > > salt:timestamp and rows goes like this:
> > > ...
> > > 1:15
> > > 1:16
> > > 1:17
> > > 1:23
> > > 2:3
> > > 2:5
> > > 2:12
> > > 2:15
> > > 2:19
> > > 2:25
> > > ...
> > >
> > > And I want to find all rows, that has second part (timestamp) in range
> > > 15-25. What startKey and endKey should be used?
> > >
> > > Alexandr Vasilenko
> > > Web Developer
> > > Skype:menterr
> > > mob: +38097-611-45-99
> > >
> > > 2012/2/9 lars hofhansl <lhofhansl@...>
> > Hi,
> > Alexandr Vasilenko
> > Have you ever resolved this issue?i am also facing this iusse.
> > i also want implement this functionality.
> > Imagine row key of format
> > salt:timestamp and rows goes like this:
> > ...
> > 1:15
> > 1:16
> > 1:17
> > 1:23
> > 2:3
> > 2:5
> > 2:12
> > 2:15
> > 2:19
> > 2:25
> > ...
> >
> > And I want to find all rows, that has second part (timestamp) in range
> > 15-25.
> >
> > Could you please tell me how you resolve this ?
> > thanks  in advance.
> >
> >
> > Tony duan
> >
> >
>
>
> --
> Regards,
> Premal Shah.
>

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