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

Hakim commented on SOLR-5787:
-----------------------------

Actually, I am using the `q` parameter for my query instead of the filter query 
`fq`. And documents count of suggestions proposed is relative to all index, 
instead of being relative to the query
For example, if I'm searching for `q` = 'town:usa AND search:ferraro', and that 
there are 100 ferrari in the whole world but only 10 of them are in the usa.
The suggestion 'ferrari' would have a count of 100 even if my request is 
restricted to usa (instead of 10).

> Get spellcheck frequency relatively to current query
> ----------------------------------------------------
>
>                 Key: SOLR-5787
>                 URL: https://issues.apache.org/jira/browse/SOLR-5787
>             Project: Solr
>          Issue Type: Improvement
>          Components: spellchecker
>    Affects Versions: 4.6
>         Environment: Solr deployed on Jetty 9 Servlet container
>            Reporter: Hakim
>            Priority: Minor
>              Labels: features, newbie
>
> I guess that this functionnality isn't implemented yet. I'll begin by an 
> example to explain what I'm requesting:
> I have a lucene query that get articles satisfying a certain query. With this 
> same command, I'm getting at the same time suggestions if this query doesnt 
> return any article (so far, nothing unusual). 
> The frequency (count) associated with these suggestions is relative to all 
> index (it counts all occurences of the suggestion in the whole index). What I 
> want is that it counts only suggestion occurences satisfying current lucene 
> query.
> P.S: I'm using solr's spellcheck component (solr.DirectSolrSpellChecker).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to