Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 25 Dec 2013 00:09:51 +0000 (UTC)
From: "Alex Baranau (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12604107.1345491902257.9356.1387930191200@arcas>
In-Reply-To: <JIRA.12604107.1345491902257@arcas>
References: <JIRA.12604107.1345491902257@arcas>
Subject: [jira] [Commented] (HBASE-6618) Implement FuzzyRowFilter with
 ranges support
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alex Baranau commented on HBASE-6618:
-------------------------------------

Yeah, looks like nobody looked at the patch, even though I know others use it (patch). Weird and don't know how to push anyone to do that.

Not sure if patch fits latest version. If there's still an interest from any committer (I hope so) to take a look and proceed with the issue, I will take a look at it and make sure it is good for latest version.

> 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
>             Fix For: 0.99.0
>
>         Attachments: HBASE-6618-algo-desc-bits.png, HBASE-6618-algo.patch, HBASE-6618.patch, HBASE-6618_2.path, HBASE-6618_3.path
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)