That should not be the case, Maybe the analysis-chain of 'text_spell' is doing something before the key hits the suggester (you want to use something like KeywordTokenizerFactory)? Also maybe specify the queryAnalyzerFieldType in the suggest component config? you might want to do something similar to solr-config: ( https://github.com/apache/lucene-solr/blob/trunk/solr/core/src/test-files/solr/collection1/conf/solrconfig-phrasesuggest.xml) [look at suggest_analyzing component] and schema: ( https://github.com/apache/lucene-solr/blob/trunk/solr/core/src/test-files/solr/collection1/conf/schema-phrasesuggest.xml) [look at phrase_suggest field type].
On Mon, Feb 10, 2014 at 8:44 PM, Hamish Campbell < hamish.campb...@koordinates.com> wrote: > Same issue with AnalyzingLookupFactory - I'll get autocomplete suggestions > but not the original query. > > > On Tue, Feb 11, 2014 at 1:57 PM, Areek Zillur <areek...@gmail.com> wrote: > > > The FuzzyLookupFactory should accept all the options as that of as > > AnalyzingLookupFactory ( > > > > > http://lucene.apache.org/solr/4_2_1/solr-core/org/apache/solr/spelling/suggest/fst/AnalyzingLookupFactory.html > > ). > > [FuzzySuggester is a direct subclass of the AnalyzingSuggester in > lucene]. > > Have you tried the exactMatchFirst with the AnalyzingLookupFactory? Does > > AnalyzingLookup have the same problem with the exactMatchFirst option? > > > > > > On Mon, Feb 10, 2014 at 6:00 PM, Hamish Campbell < > > hamish.campb...@koordinates.com> wrote: > > > > > Looking at: > > > > > > > > > > > > http://lucene.apache.org/solr/4_2_1/solr-core/org/apache/solr/spelling/suggest/fst/FuzzyLookupFactory.html > > > > > > It seems that exactMatchFirst is not a valid option for > > FuzzyLookupFactory. > > > Potential workarounds? > > > > > > > > > On Mon, Feb 10, 2014 at 5:04 PM, Hamish Campbell < > > > hamish.campb...@koordinates.com> wrote: > > > > > > > Hi all, > > > > > > > > I've got a FuzzyLookupFactory spellchecker with exactMatchFirst > > enabled. > > > A > > > > query like "tes" will return "test" and "testing", but a query for > > "test" > > > > will *not* return "test" even though it is clearly in the dictionary. > > Why > > > > would this be? > > > > > > > > Relevant config follows > > > > > > > > <searchComponent class="solr.SpellCheckComponent" name="suggest"> > > > > <lst name="spellchecker"> > > > > <str name="name">suggest</str> > > > > > > > > <!-- Implementation --> > > > > <str > > > > name="classname">org.apache.solr.spelling.suggest.Suggester</str> > > > > <str > > > > > > > > > > name="lookupImpl">org.apache.solr.spelling.suggest.fst.FuzzyLookupFactory</str> > > > > > > > > <!-- Properties --> > > > > <bool name="preserveSep">false</bool> > > > > <bool name="exactMatchFirst">true</bool> > > > > <str name="suggestAnalyzerFieldType">text_spell</str> > > > > <float name="threshold">0.005</float> > > > > > > > > <!-- > > > > Do not build on each commit, bad for performance. See cron. > > > > <str name="buildOnCommit">false</str> > > > > --> > > > > > > > > <!-- Source --> > > > > <str name="field">suggest</str> > > > > </lst> > > > > </searchComponent> > > > > > > > > <requestHandler name="/suggest" class="solr.SearchHandler"> > > > > <lst name="defaults"> > > > > <str name="spellcheck">true</str> > > > > <str name="spellcheck.dictionary">suggest</str> > > > > <str name="spellcheck.onlyMorePopular">true</str> > > > > <str name="spellcheck.count">5</str> > > > > <str name="spellcheck.collate">true</str> > > > > </lst> > > > > > > > > <arr name="components"> > > > > <str>suggest</str> > > > > </arr> > > > > </requestHandler> > > > > > > > > -- > > > > Hamish Campbell > > > > Koordinates Ltd <http://koordinates.com/?_bzhc=esig> > > > > PH +64 9 966 0433 > > > > FAX +64 9 966 0045 > > > > > > > > > > > > > > > > -- > > > Hamish Campbell > > > Koordinates Ltd <http://koordinates.com/?_bzhc=esig> > > > PH +64 9 966 0433 > > > FAX +64 9 966 0045 > > > > > > > > > -- > Hamish Campbell > Koordinates Ltd <http://koordinates.com/?_bzhc=esig> > PH +64 9 966 0433 > FAX +64 9 966 0045 >
