[
https://issues.apache.org/jira/browse/HBASE-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561963#comment-13561963
]
Hudson commented on HBASE-6509:
-------------------------------
Integrated in HBase-0.94 #766 (See
[https://builds.apache.org/job/HBase-0.94/766/])
HBASE-7628 Port HBASE-6509 fast-forwarding FuzzyRowFilter to 0.94 (Anoop)
(Revision 1438114)
Result = SUCCESS
tedyu :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/filter/FuzzyRowFilter.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/io/HbaseObjectWritable.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/filter/TestFuzzyRowFilter.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/io/TestHbaseObjectWritable.java
> Implement fast-forwarding FuzzyRowFilter to allow filtering rows e.g. by
> "???alex?b"
> ------------------------------------------------------------------------------------
>
> Key: HBASE-6509
> URL: https://issues.apache.org/jira/browse/HBASE-6509
> Project: HBase
> Issue Type: New Feature
> Components: Filters
> Reporter: Alex Baranau
> Assignee: Alex Baranau
> Priority: Minor
> Fix For: 0.96.0
>
> Attachments: HBASE-6509_1.patch, HBASE-6509_2.patch,
> HBASE-6509_3.patch, HBASE-6509.patch
>
>
> Implement fuzzy row key filter to allow fetching records e.g. by this
> criteria: "???alex?b".
> This seems to be very useful as an alternative to select records by row keys
> by specifying their part which is not prefix part. Due to fast-forwarding
> nature of the filter in many situations this helps to avoid heavy full-table
> scans.
> This is especially effective when you have composite row key and (some of)
> its parts has fixed length. E.g. with the key of format userId_actionId_time,
> given that userId and actionId length is fixed, one can select user actions
> of specific type using fuzzy row key by specifying mask "????_myaction".
> Given fast-forwarding nature of filter, this will usually work much faster
> than doing whole table scan with any of the existing server-side filters.
> In many cases this can work as secondary-indexing alternative.
> Many times users implement it as a custom filter and many times they just
> don' know this is possible. Let's add it to the common codebase.
--
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
