[
https://issues.apache.org/jira/browse/LUCENE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104354#comment-17104354
]
Michael McCandless commented on LUCENE-9365:
--------------------------------------------
{quote}{quote}Maybe we should disallow prefix == term.text().length() for
FuzzyQuery? It is sort of strange to use FuzzyQuery in this way
{quote}
I guess that the downside of this approach is that it pushes the burden to the
application? I would expect users to have a global prefix length that they
apply to all fuzzy queries. Disallowing prefix >= term.length would require
consumers of the API to check the length of the string that they are searching
for, which would be prone to the usual errors, e.g. should it be counting java
chars or unicode code points.
{quote}
OK I agree that's a hassle / risky bug inducing to application code, so +1 to
make {{FuzzyQuery}} lenient to these cases and rewrite itself to
{{PrefixQuery}} or {{RegexpQuery}} instead.
> Fuzzy query has a false negative when prefix length == search term length
> --------------------------------------------------------------------------
>
> Key: LUCENE-9365
> URL: https://issues.apache.org/jira/browse/LUCENE-9365
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/query/scoring
> Reporter: Mark Harwood
> Priority: Major
>
> When using FuzzyQuery the search string `bba` does not match doc value `bbab`
> with an edit distance of 1 and prefix length of 3.
> In FuzzyQuery an automaton is created for the "suffix" part of the search
> string which in this case is an empty string.
> In this scenario maybe the FuzzyQuery should rewrite to a WildcardQuery of
> the following form :
> {code:java}
> searchString + "?"
> {code}
> .. where there's an appropriate number of ? characters according to the edit
> distance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
