[
https://issues.apache.org/jira/browse/HBASE-10027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832908#comment-13832908
]
Manukranth Kolloju commented on HBASE-10027:
--------------------------------------------
Yeah, seems like the the following compound row prefix filter:
{[a,b,c], [d,e,f], [d,e], [m,n,o]}
can be translated to
{ { [a,b,c] -> [0, 0, 0] }, { [d,e,] -> [0, 0] }, { [m,n,o] -> [0, 0, 0] } }
I can just create a Facade builder and reuse the FuzzyRowFilter from Open
Source underneath then.
> CompoundRowPrefixFilter
> -----------------------
>
> Key: HBASE-10027
> URL: https://issues.apache.org/jira/browse/HBASE-10027
> Project: HBase
> Issue Type: New Feature
> Components: Filters
> Affects Versions: 0.89-fb
> Reporter: Manukranth Kolloju
> Assignee: Manukranth Kolloju
> Fix For: 0.89-fb
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> In order to scan a sequence of row prefixes optimally, this filter will
> provide a hint to the Scanner via the scan query matcher to go to the next
> prefix after finishing scanning with the current range.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
