You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2023/09/07 09:26:00 UTC

[jira] [Commented] (HBASE-12222) FuzzyRowFilter unpredictable with jagged rowkeys

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

Nick Dimiduk commented on HBASE-12222:
--------------------------------------

[~dethi] Given how picky the current implementation is, we may be better served by introducing a new filter implementation that defines a more strict contract. 

> FuzzyRowFilter unpredictable with jagged rowkeys
> ------------------------------------------------
>
>                 Key: HBASE-12222
>                 URL: https://issues.apache.org/jira/browse/HBASE-12222
>             Project: HBase
>          Issue Type: Bug
>          Components: Filters
>            Reporter: Nick Dimiduk
>            Priority: Major
>         Attachments: 12222_tests.patch
>
>
> FuzzyRowFilter getNextCellHint doesn't take into account jagged rowkeys and produces surprising results. For example, given a table of
> {noformat}
> 0
> 0/0
> 0/1
> 0/2
> 1
> 1/0
> 1/1
> 1/2
> 2
> 2/0
> 2/1
> 2/2
> {noformat}
> and FuzzyPrefixFilter like "?/2", {1, 0, 0}
> I would expect
> {noformat}
> 0/2
> 1/2
> 2/2
> {noformat}
> The results include the rows '0', '1', and '2'



--
This message was sent by Atlassian Jira
(v8.20.10#820010)