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

Nalini Kartha commented on SOLR-5787:
-------------------------------------

[~h4k1m] I think the functionality you're looking for is exposed through 
collations as [~jdyer] explained. In order to get suggestion frequencies taking 
into account the rest of query terms, a query needs to be run and that's 
exactly what collations does - the frequency returned with collations is what 
you're looking for. So should we close this JIRA? I'll open another one for the 
fq param issue discussed above.

> 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