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

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

Ah, sorry, haven't said anything about that. For toInc - we may not change it 
at every step, so if there's a missing arrow, that means nothing should be 
changed.

Thanx for checking out!

One thing that I'm not 100% sure about - is it better to adjust current 
FuzzyRowFilter and this functionality to it or add new. I'm leaning towards 
adjusting FuzzyRowFilter as this new feature fits naturally in it. Thoughts?
                
> 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
>            Priority: Minor
>         Attachments: HBASE-6618-algo-desc-bits.png, HBASE-6618-algo.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: 
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