Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Thu, 14 Feb 2013 16:16:14 +0000 (UTC)
From: "Markus Jelsma (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12626423.1357596746442.289257.1360858574484@arcas>
In-Reply-To: <JIRA.12626423.1357596746442@arcas>
References: <JIRA.12626423.1357596746442@arcas>
Subject: [jira] [Commented] (SOLR-4280) spellcheck.maxResultsForSuggest
 based on filter query results
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578460#comment-13578460 ] 

Markus Jelsma commented on SOLR-4280:
-------------------------------------

Hi James,

I'm not sure that i follow. This patch only obtains the number of results for a given. If the user has a single filter in the query lang:nl this patch looks up the number of results for that filter only. The same is true for multiple filters e.g. fq=lang:en&fq=host:apache.org, it just iterates over the these filters in the cache and gets the number of documents they can return.

How would a user misuse this feature? This patch does not write to the filterCache, users do so by adding fq-parameters.

Thanks
                
> spellcheck.maxResultsForSuggest based on filter query results
> -------------------------------------------------------------
>
>                 Key: SOLR-4280
>                 URL: https://issues.apache.org/jira/browse/SOLR-4280
>             Project: Solr
>          Issue Type: Improvement
>          Components: spellchecker
>            Reporter: Markus Jelsma
>             Fix For: 4.2, 5.0
>
>         Attachments: SOLR-4280-trunk-1.patch
>
>
> spellcheck.maxResultsForSuggest takes a fixed number but ideally should be able to take a ratio and calculate that against the maximum number of results the filter queries return.
> At least in our case this would certainly add a lot of value. >99% of our end-users search within one or more filters of which one is always unique. The number of documents for each of those unique filters varies significantly ranging from 300 to 3.000.000 documents in which they search. The maxResultsForSuggest is set to a reasonable low value so it kind of works fine but sometimes leads to undesired suggestions for a large subcorpus that has more misspellings.
> Spun off from SOLR-4278.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org