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

Rajesh Kapur commented on SOLR-8928:
------------------------------------

Hi,

I am using SOLR Ver 6.0.0 and updated the techproducts example configuration 
for suggestion to:
<searchComponent name="suggest" class="solr.SuggestComponent">
        <lst name="suggester">
                <str name="name">mySuggester</str>
                <str name="lookupImpl">AnalyzingInfixLookupFactory</str>
                <str name="dictionaryImpl">DocumentDictionaryFactory</str>
                <str name="field">name</str>
                <str name="weightField">price</str>
                <str name="contextField">cat</str>
                <str name="suggestAnalyzerFieldType">string</str>
                <str name="buildOnStartup">false</str>
        </lst>
  </searchComponent> 

Still I am not able to get the desired output using below query:
http://localhost:8983/solr/techproducts/suggest?suggest=true&suggest.build=true&suggest.dictionary=mySuggester&wt=json&suggest.q=c&suggest.cfq=memory

Could you please help me.

> suggest.cfq does not work with 
> DocumentExpressionDictionaryFactory/weightExpression
> -----------------------------------------------------------------------------------
>
>                 Key: SOLR-8928
>                 URL: https://issues.apache.org/jira/browse/SOLR-8928
>             Project: Solr
>          Issue Type: Bug
>          Components: Suggester
>    Affects Versions: 5.5
>            Reporter: jmlucjav
>
> Using BlendedInfixLookupFactory, trying to use  
> DocumentExpressionDictionaryFactory/weightExpression with suggest.cfq does 
> not work. No docs get returned, even the ones that comply with the cfq.
> Moving to DocumentDictionaryFactory/weightField fixes this.



--
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