lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Otis Gospodnetic (JIRA)" <>
Subject [jira] Resolved: (LUCENE-786) Extended javadocs in spellchecker
Date Fri, 02 Mar 2007 18:30:50 GMT


Otis Gospodnetic resolved LUCENE-786.

       Resolution: Fixed
    Lucene Fields: [New, Patch Available]  (was: [Patch Available, New])

Applied, merci Karl.

> Extended javadocs in spellchecker
> ---------------------------------
>                 Key: LUCENE-786
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Javadocs
>    Affects Versions: 2.0.0
>            Reporter: Karl Wettin
>         Assigned To: Otis Gospodnetic
>            Priority: Trivial
>         Attachments: spellcheck_javadocs.diff
> Added some javadocs that explains why the spellchecker does not work as one might expect
it to.
> > Without having looked at the code for a long time, I think the problem is what the
> > lucene scoring consider to be best. First the grams are searched, resulting in a
> > of hits. Then the edit-distance is calculated on each hit. "Genetics" is appearently
> > third most similar hit according to Lucene, but the best according to Levenshtein.
> >
> > I.e. Lucene does not use edit-distance as similarity. You need to get a bunch of
best hits
> > in order to find the one with the smallest edit-distance.
> I took a look at the code, and my assessment seems to be right.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message