lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Krupansky (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4024) FuzzyQuery should never do edit distance > 2
Date Mon, 07 May 2012 19:20:51 GMT


Jack Krupansky commented on LUCENE-4024:

bq. The levenshtein distance has changed to include transposition as a primitive edit

Is there any user-visible doc about that change? I don't see any mention in CHANGES.txt or
the Javadoc for FuzzyQuery.

At least according to the Wikipedia, the addition of transposition as a primitive would be
referred to as the "Damerau–Levenshtein distance".

At least the Javadoc for FuzzyQuery should have a link to whatever the technically correct
specification is.

A few examples would be nice as well.

> FuzzyQuery should never do edit distance > 2
> --------------------------------------------
>                 Key: LUCENE-4024
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>             Fix For: 4.0
>         Attachments: LUCENE-4024.patch
> Edit distance 1 and 2 are now very very fast compared to 3.x (100X-200X faster) ... but
edit distance 3 will fallback to the super-slow scan all terms in 3.x, which is not graceful
> Not sure how to fix it ... mabye we have a SlowFuzzyQuery?  And FuzzyQuery throws exc
if you try to ask it to be slow?  Or, we add boolean (off by default) that you must turn on
to allow slow one..?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message