lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Naber (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-1676) spellcheck.count has confusing default and documentation
Date Mon, 21 Dec 2009 14:18:18 GMT

     [ https://issues.apache.org/jira/browse/SOLR-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Naber updated SOLR-1676:
-------------------------------

    Attachment: solr-spellcheck.diff

Here's a suggestion on how we could modify the documentation (i.e. the sample config): mention
that the limit might need to be increased, and set the default value to 5. I see there are
many more solrconfig.xml files in the test directory, I'm not sure if those would need to
be modified, too.

> spellcheck.count has confusing default and documentation
> --------------------------------------------------------
>
>                 Key: SOLR-1676
>                 URL: https://issues.apache.org/jira/browse/SOLR-1676
>             Project: Solr
>          Issue Type: Bug
>          Components: spellchecker
>    Affects Versions: 1.4
>            Reporter: Daniel Naber
>            Assignee: Shalin Shekhar Mangar
>            Priority: Minor
>         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.


Mime
View raw message