hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-6618) Implement FuzzyRowFilter with ranges support
Date Fri, 08 Mar 2013 02:56:17 GMT

    [ https://issues.apache.org/jira/browse/HBASE-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596734#comment-13596734

Ted Yu edited comment on HBASE-6618 at 3/8/13 2:55 AM:

bq. skip hint as ['foobar'][4000] (i.e. 
{code}'foobar' + new byte[] {0} + new byte[] {1,0,0,0}
Is there a typo above ?
Should it be:
'foobar' + new byte[] {0} + new byte[] {4,0,0,0}
      was (Author: yuzhihong@gmail.com):
    bq. skip hint as ['foobar'][4000] (i.e. 'foobar' + new byte[] {0} + new byte[] {1,0,0,0}).
Is there a typo above ?
Should it be:
'foobar' + new byte[] {0} + new byte[] {4,0,0,0}
> Implement FuzzyRowFilter with ranges support
> --------------------------------------------
>                 Key: HBASE-6618
>                 URL: https://issues.apache.org/jira/browse/HBASE-6618
>             Project: HBase
>          Issue Type: New Feature
>          Components: Filters
>            Reporter: Alex Baranau
>            Assignee: Alex Baranau
>            Priority: Minor
>         Attachments: HBASE-6618_2.path, HBASE-6618_3.path, HBASE-6618-algo-desc-bits.png,
HBASE-6618-algo.patch, HBASE-6618.patch
> Apart from current ability to specify fuzzy row filter e.g. for <userId_actionId>
format as ????_0004 (where 0004 - actionId) it would be great to also have ability to specify
the "fuzzy range" , e.g. ????_0004, ..., ????_0099.
> See initial discussion here: http://search-hadoop.com/m/WVLJdX0Z65
> Note: currently it is possible to provide multiple fuzzy row rules to existing FuzzyRowFilter,
but in case when the range is big (contains thousands of values) it is not efficient.
> Filter should perform efficient fast-forwarding during the scan (this is what distinguishes
it from regex row filter).
> While such functionality may seem like a proper fit for custom filter (i.e. not including
into standard filter set) it looks like the filter may be very re-useable. We may judge based
on the implementation that will hopefully be added.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message