lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <>
Subject [jira] Resolved: (SOLR-1676) spellcheck.count has confusing default and documentation
Date Thu, 24 Dec 2009 06:37:29 GMT


Shalin Shekhar Mangar resolved SOLR-1676.

       Resolution: Fixed
    Fix Version/s: 1.5

Committed revision 893700.

I've added a note in the example solrconfig.xml to refer to the wiki for details on the request

Thanks Daniel!

> spellcheck.count has confusing default and documentation
> --------------------------------------------------------
>                 Key: SOLR-1676
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: spellchecker
>    Affects Versions: 1.4
>            Reporter: Daniel Naber
>            Assignee: Shalin Shekhar Mangar
>            Priority: Minor
>             Fix For: 1.5
>         Attachments: solr-spellcheck.diff
> It seems spellcheck.count does not just limit the number of results returned, as the
documentation claims. Instead, this value is given to the Lucene SpellChecker class which
multiplies it by 10 and then only fetches the first spellcheck.count*10 candidates, ignoring
all others. The effect is that with a low value for spellcheck.count you might miss good hits.
In other words, the first item with spellcheck.count==1 is not always the same item as with
e.g. spellcheck.count==10.
> The fix could be to fix the documentation (the comments in the sample solrconfig.xml)
to mention this and use a better default.
> The Lucene SpellChecker class says about the numSug parameter: "Thus, you should set
this value to *at least* 5 for a good suggestion."

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

View raw message