You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Clemens Wyss DEV <cl...@mysign.ch> on 2018/09/03 10:58:06 UTC
AW: Solr suggestions: why are exact matches omitted
Sorry for not giving up on this issue:
is this "behavior" a feature or a bug?
-----Ursprüngliche Nachricht-----
Von: Clemens Wyss DEV <cl...@mysign.ch>
Gesendet: Donnerstag, 30. August 2018 18:01
An: 'solr-user@lucene.apache.org' <so...@lucene.apache.org>
Betreff: Solr suggestions: why are exact matches omitted
Given the following configuration:
...
<searchComponent name="suggest_word" class="solr.SpellCheckComponent">
<lst name="spellchecker">
<str name="name">suggest_word_fuzzy</str>
<str name="classname">org.apache.solr.spelling.suggest.Suggester</str>
<str name="lookupImpl">org.apache.solr.spelling.suggest.fst.FuzzyLookupFactory</str>
<str name="ignoreCase=">true</str>
<str name="field">_my_suggest_word</str>
<str name="maxEdits">2</str>
<float name="maxQueryFrequency">0.01</float>
<float name="thresholdTokenFrequency">.01</float> <!-- muss mind in 0.01% der Dokumente vorkommen -->
<str name="suggestAnalyzerFieldType">suggest_word</str> <!-- -->
<!-- <str name="storeDir">suggest_word_fuzzy</str> -->
<str name="buildOnOptimize">false</str> <!-- ?? -->
<str name="buildOnStartup">false</str> <!-- ?? -->
<str name="buildOnCommit">true</str> <!-- das brauchen wir -->
</lst>
</searchComponent>
...
When I try to find suggestions for "11000.35" I get
"11000.33"
"11000.34"
"11000.36"
"11000.37"
...
but not "11000.35", although "11000.35" exists (and is suggested when I for example type "11000.34")
Thx in advance
- Clemens
AW: Solr suggestions: why are exact matches omitted
Posted by Clemens Wyss DEV <cl...@mysign.ch>.
> I'm afraid only thorough debugging might answer
I'd say debugging is only required if everybody (not just me 😉) expects to get "the exact match" in the spellcheck-response ... If it's nonsense to expect "the exact match" in the spellcheck-respons, then it's a feature of spellchecking
-----Ursprüngliche Nachricht-----
Von: Mikhail Khludnev <mk...@apache.org>
Gesendet: Montag, 3. September 2018 13:17
An: solr-user <so...@lucene.apache.org>
Betreff: Re: Solr suggestions: why are exact matches omitted
I'm afraid only thorough debugging might answer.
On Mon, Sep 3, 2018 at 1:58 PM Clemens Wyss DEV <cl...@mysign.ch>
wrote:
> Sorry for not giving up on this issue:
> is this "behavior" a feature or a bug?
>
> -----Ursprüngliche Nachricht-----
> Von: Clemens Wyss DEV <cl...@mysign.ch>
> Gesendet: Donnerstag, 30. August 2018 18:01
> An: 'solr-user@lucene.apache.org' <so...@lucene.apache.org>
> Betreff: Solr suggestions: why are exact matches omitted
>
> Given the following configuration:
> ...
> <searchComponent name="suggest_word" class="solr.SpellCheckComponent">
> <lst name="spellchecker">
> <str name="name">suggest_word_fuzzy</str>
> <str
> name="classname">org.apache.solr.spelling.suggest.Suggester</str>
> <str
> name="lookupImpl">org.apache.solr.spelling.suggest.fst.FuzzyLookupFactory</str>
> <str name="ignoreCase=">true</str>
> <str name="field">_my_suggest_word</str>
> <str name="maxEdits">2</str>
> <float name="maxQueryFrequency">0.01</float>
> <float name="thresholdTokenFrequency">.01</float> <!--
> muss mind in 0.01% der Dokumente vorkommen -->
> <str
> name="suggestAnalyzerFieldType">suggest_word</str>
> <!-- -->
> <!-- <str name="storeDir">suggest_word_fuzzy</str> -->
> <str name="buildOnOptimize">false</str> <!-- ?? -->
> <str name="buildOnStartup">false</str> <!-- ?? -->
> <str name="buildOnCommit">true</str> <!-- das brauchen
> wir
> -->
> </lst>
> </searchComponent>
> ...
> When I try to find suggestions for "11000.35" I get "11000.33"
> "11000.34"
> "11000.36"
> "11000.37"
> ...
> but not "11000.35", although "11000.35" exists (and is suggested when
> I for example type "11000.34")
>
> Thx in advance
> - Clemens
>
--
Sincerely yours
Mikhail Khludnev
Re: Solr suggestions: why are exact matches omitted
Posted by Mikhail Khludnev <mk...@apache.org>.
I'm afraid only thorough debugging might answer.
On Mon, Sep 3, 2018 at 1:58 PM Clemens Wyss DEV <cl...@mysign.ch>
wrote:
> Sorry for not giving up on this issue:
> is this "behavior" a feature or a bug?
>
> -----Ursprüngliche Nachricht-----
> Von: Clemens Wyss DEV <cl...@mysign.ch>
> Gesendet: Donnerstag, 30. August 2018 18:01
> An: 'solr-user@lucene.apache.org' <so...@lucene.apache.org>
> Betreff: Solr suggestions: why are exact matches omitted
>
> Given the following configuration:
> ...
> <searchComponent name="suggest_word" class="solr.SpellCheckComponent">
> <lst name="spellchecker">
> <str name="name">suggest_word_fuzzy</str>
> <str
> name="classname">org.apache.solr.spelling.suggest.Suggester</str>
> <str
> name="lookupImpl">org.apache.solr.spelling.suggest.fst.FuzzyLookupFactory</str>
> <str name="ignoreCase=">true</str>
> <str name="field">_my_suggest_word</str>
> <str name="maxEdits">2</str>
> <float name="maxQueryFrequency">0.01</float>
> <float name="thresholdTokenFrequency">.01</float> <!--
> muss mind in 0.01% der Dokumente vorkommen -->
> <str name="suggestAnalyzerFieldType">suggest_word</str>
> <!-- -->
> <!-- <str name="storeDir">suggest_word_fuzzy</str> -->
> <str name="buildOnOptimize">false</str> <!-- ?? -->
> <str name="buildOnStartup">false</str> <!-- ?? -->
> <str name="buildOnCommit">true</str> <!-- das brauchen wir
> -->
> </lst>
> </searchComponent>
> ...
> When I try to find suggestions for "11000.35" I get
> "11000.33"
> "11000.34"
> "11000.36"
> "11000.37"
> ...
> but not "11000.35", although "11000.35" exists (and is suggested when I
> for example type "11000.34")
>
> Thx in advance
> - Clemens
>
--
Sincerely yours
Mikhail Khludnev