On 17 December 2014 at 16:41, Erick Erickson <erickerick...@gmail.com> wrote:
> First, I'd look in your corpus for "bnak". The problem with index-based
> suggestions is that if your index contains garbage, they're "correctly
> spelled" since they're in the index. TermsComponent is very useful for this.
>
> You can also loosen up the match criteria, and as I remember the collations
> parameter does some permutations of the word (but my memory of how that
> works is shaky).
Thank you for your response. I now set up a TermsComponent for this
case as follows:
<searchComponent name="termsComponent" class="solr.TermsComponent”/>
<requestHandler name="terms" class="solr.SearchHandler">
<lst name="defaults">
<bool name="terms">true</bool>
<str name="terms.fl">text</str>
</lst>
<arr name="components">
<str>termsComponent</str>
</arr>
</requestHandler>
… constructed a MapSolrParams from which I create my
SolrQueryRequestBase object using these params (“text” is the name of
my catch-all-field):
{{params(terms.prefix="bnak"),defaults(terms.fl=text&terms=true)}}
… and call my core with it, yielding the following:
{responseHeader={status=0,QTime=5416},terms={text={}}}
That seems to imply that indeed the term “bnak” is not in my index, or
am I using the TermsComponent the wrong way?
Cheers,
Martin
--
---------- mdie...@gmail.com --/-- mar...@the-little-red-haired-girl.org ----
------------- / http://herbert.the-little-red-haired-girl.org / -------------
