[ 
https://issues.apache.org/jira/browse/HBASE-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Baranau updated HBASE-6509:
--------------------------------

    Attachment: HBASE-6509.patch

Attached patch. Also created review request at 
https://reviews.apache.org/r/6354/. More unit-tests to come (see review).

Please let me know your thoughts about API. I feel like setting mask (0s and 1s 
only currently) via byte[] is might be overkill. Not sure if we'll need more 
states for values. Using byte[] just looked handy to me from the client 
prospective at the time I implemented this initially (some time ago)
                
> Implement fast-forwarding FuzzyRowFilter to allow filter 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
>         Attachments: 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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to