Ah, I think the term frequency is only available for the Spellcheckers
rather than the Suggesters - so I tried a DirectSolrSpellChecker. This gave
me good spelling suggestions for misspelt terms, but if the term is spelled
correctly I, again, get no term information and correctlySpelled is false.
B
I've tried the new SuggestComponent, however it doesn't work quite as
expected. It returns the full field value rather than a list of corrections
for the specific term. I can see how SuggestComponent would be excellent
for phrase suggestions and document lookups, but it doesn't seem to be
suitable
Dont worry about the analysis chain, I realized you are using the
spellcheck component for suggestions. The suggestion gets returned from the
Lucene layer, but unfortunately the Spellcheck component strips the
suggestion out as it is mainly built for spell checking (when the query
token == suggesti
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
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 wrote:
> The FuzzyLookupFactory should accept all the options as that of as
> AnalyzingLookupFactory (
>
> http://lucene.apache.org/solr/4_2_1/sol
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
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...@koordinate
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
suggest
