[
https://issues.apache.org/jira/browse/HBASE-7892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584999#comment-13584999
]
Ted Yu commented on HBASE-7892:
-------------------------------
@Maryann:
Do you mind rebasing your patch ?
{code}
patching file src/main/java/org/apache/hadoop/hbase/filter/FuzzyRowFilter.java
Hunk #1 FAILED at 68.
Hunk #2 FAILED at 106.
Hunk #3 FAILED at 183.
Hunk #4 FAILED at 233.
Hunk #5 FAILED at 270.
5 out of 5 hunks FAILED -- saving rejects to file
src/main/java/org/apache/hadoop/hbase/filter/FuzzyRowFilter.java.rej
(Stripping trailing CRs from patch.)
patching file
src/test/java/org/apache/hadoop/hbase/filter/TestFuzzyRowFilter.java
Hunk #1 FAILED at 174.
1 out of 1 hunk FAILED -- saving rejects to file
src/test/java/org/apache/hadoop/hbase/filter/TestFuzzyRowFilter.java.rej
{code}
> FuzzyRowFilter would have wrong behaviors if user gives an arbitary byte for
> an "unfixed" position instead of byte 0
> --------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-7892
> URL: https://issues.apache.org/jira/browse/HBASE-7892
> Project: HBase
> Issue Type: Improvement
> Components: Filters
> Affects Versions: 0.96.0, 0.94.5
> Reporter: Maryann Xue
> Assignee: Maryann Xue
> Priority: Minor
> Attachments: HBASE-7892-0.94.patch
>
>
> An actual case can be:
> we want to match "a?ex", so we give "a?ex" as input of "key bytes", and
> "0100" as input of "meta bytes".
> if we start with row = "\0\0\0\0", the next hint would turn out to be "a?ex"
> while actually the right hint should be "a\0ex".
--
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
