Re: Solr suggestions, best practices

2018-11-06 Thread Zheng Lin Edwin Yeo
Maybe you can look into this:
https://lucidworks.com/2015/03/04/solr-suggester/

Which version of Solr are you using?

Regards,
Edwin

On Tue, 6 Nov 2018 at 17:00, Clemens Wyss DEV  wrote:

> At the moment we are using spellchecking-component for suggestions which
> is suboptimal, to say the least. What are best pracitces for suggestions
> using Solr?
> googling (with excellent suggestions ) I came along
>
> https://blog.trifork.com/2012/02/15/different-ways-to-make-auto-suggestions-with-solr/
> and
>
> https://grokbase.com/t/lucene/solr-user/14bayc6jkc/best-practice-autosuggest-autocomplete-vs-real-search
>
> Any other valuable reads/links regarding suggestions?
>
> Thx in advance
> - Clemens
>


Re: Solr suggestions: why are exact matches omitted

2018-09-03 Thread Mikhail Khludnev
I'm afraid only thorough debugging might answer.

On Mon, Sep 3, 2018 at 1:58 PM Clemens Wyss DEV 
wrote:

> Sorry for not giving up on this issue:
> is this "behavior" a feature or a bug?
>
> -Ursprüngliche Nachricht-
> Von: Clemens Wyss DEV 
> Gesendet: Donnerstag, 30. August 2018 18:01
> An: 'solr-user@lucene.apache.org' 
> Betreff: Solr suggestions: why are exact matches omitted
>
> Given the following configuration:
> ...
> 
> 
> suggest_word_fuzzy
>  name="classname">org.apache.solr.spelling.suggest.Suggester
>  name="lookupImpl">org.apache.solr.spelling.suggest.fst.FuzzyLookupFactory
> true
> _my_suggest_word
> 2
> 0.01
> .01 
> suggest_word
> 
> 
> false 
> false 
> true 
> 
> 
> ...
> 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

2011-02-11 Thread Erick Erickson
Well, you have to tell us how you're accessing the info and what's
in your index.

Please include the relevant schema file definitions and the calls you're
making to get spelling suggestions.

Best
Erick

On Fri, Feb 11, 2011 at 8:55 AM, Thumuluri, Sai
sai.thumul...@verizonwireless.com wrote:
 Good Morning,
 I have implemented Solr 1.4.1 in our UAT environment and I get weird
 suggestions for any misspellings. For instance when I search for
 cabinet award winders as opposed to cabinet award winners, I get a
 suggestion of cabinet abarc pindeks
 http://nextgen-uat.sdc.vzwcorp.com/search/apachesolr_search/cabinet%20a
 barc%20pindeks . How can I get more meaningful suggestions? Any help
 is greatly appreciated.

 Thanks,
 Sai Thumuluri





RE: Solr suggestions

2011-02-11 Thread Thumuluri, Sai
=true stored=false
/ 
  field name=prefix2 type=prefix_token indexed=true
stored=false / 
- !--  This field is used to build the spellchecker index 
  -- 
  field name=spell type=textSpell indexed=true stored=true
multiValued=true / 
  copyField source=categories dest=categoriessrch / 
  copyField source=numcomments dest=comment_count / 
- !--  The string version of the title is used for sorting 
  -- 
  copyField source=title dest=sort_title / 
- !--  The string versions of the name used for sorting/multi-site
facets 
  -- 
  copyField source=name dest=sname / 
  copyField source=name dest=sort_name / 
- !--  Copy terms to a single field that contains all taxonomy term
names 
  -- 
  copyField source=ts_vid_* dest=taxonomy_names / 
  copyField source=content dest=body / 
  copyField source=effectivestartdate dest=created / 
- !--  Copy terms to a single field that contains all taxonomy term
names 
  -- 
  copyField source=ts_vid_* dest=taxonomy_names / 
  copyField source=effectivestartdate dest=created / 
- !--  For Wordpress 
  -- 
  copyField source=permalink dest=url / 
  copyField source=permalink dest=path / 
  copyField source=text dest=body / 
- !--  Copy the URL to Drupal's path field to make Drupal use the full
URL for the search result link 
  -- 
  copyField source=url dest=path / 
  copyField source=title dest=prefix1 / 
  copyField source=title dest=prefix2 / 
  copyField source=title dest=spell / 
  copyField source=body dest=spell / 
  copyField source=content dest=spell / 
- !--  Wordpress 
  -- 
  copyField source=text dest=spell / 
  copyField source=tags dest=spell / 
  copyField source=categories dest=spell / 
  dynamicField name=is_* type=integer indexed=true stored=true
multiValued=false / 
  dynamicField name=im_* type=integer indexed=true stored=true
multiValued=true / 
  dynamicField name=sis_* type=sint indexed=true stored=true
multiValued=false / 
  dynamicField name=sim_* type=sint indexed=true stored=true
multiValued=true / 
  dynamicField name=sm_* type=string indexed=true stored=true
multiValued=true / 
  dynamicField name=tm_* type=text indexed=true stored=true
multiValued=true termVectors=true / 
  dynamicField name=ss_* type=string indexed=true stored=true
multiValued=false / 
  dynamicField name=ts_* type=text indexed=true stored=true
multiValued=false termVectors=true / 
  dynamicField name=ds_* type=date indexed=true stored=true
multiValued=false / 
  dynamicField name=dm_* type=date indexed=true stored=true
multiValued=true / 
  dynamicField name=bm_* type=boolean indexed=true stored=true
multiValued=true / 
  dynamicField name=bs_* type=boolean indexed=true stored=true
multiValued=false / 
  dynamicField name=fs_* type=sfloat indexed=true stored=true
multiValued=false / 
  dynamicField name=fm_* type=sfloat indexed=true stored=true
multiValued=true / 
  dynamicField name=ps_* type=sdouble indexed=true stored=true
multiValued=false / 
  dynamicField name=pm_* type=sdouble indexed=true stored=true
multiValued=true / 
- !--  Wordpress Dynamic fields 
  -- 
  dynamicField name=*_i type=sint indexed=true stored=true / 
  dynamicField name=*_s type=string indexed=true stored=true /

  dynamicField name=*_l type=slong indexed=true stored=true / 
  dynamicField name=*_t type=text indexed=true stored=true / 
  dynamicField name=*_b type=boolean indexed=true stored=true
/ 
  dynamicField name=*_f type=sfloat indexed=true stored=true /

  dynamicField name=*_d type=sdouble indexed=true stored=true
/ 
  dynamicField name=*_dt type=date indexed=true stored=true / 
  dynamicField name=random* type=random / 
- !--  Sortable version of the dynamic string field 
  -- 
  dynamicField name=sort_ss_* type=sortString indexed=true
stored=false / 
  copyField source=ss_* dest=sort_ss_* / 
- !--  This field is used to store node access records, as opposed to
CCK field data 
  -- 
  dynamicField name=nodeaccess* type=integer indexed=true
stored=false multiValued=true / 
- !--  Solr to ignore all other fields 
  -- 
  dynamicField name=* type=ignored multiValued=true / 
- !--  BACKWARDS COMPATIBILITY 
  -- 
- !--  Here is where we store fields which are no longer used 
  -- 
- !--  Fields previously used for sorting  
  -- 
  field name=stitle type=string indexed=true stored=true / 
  field name=title_sort type=sortString indexed=true
stored=false / 
  field name=name_sort type=sortString indexed=true
stored=false / 
- !--  /BACKWARDS COMPATIBILITY 
  --

-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com] 
Sent: Friday, February 11, 2011 9:53 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr suggestions

Well, you have to tell us how you're accessing the info and what's
in your index.

Please include the relevant schema file definitions and the calls you're
making to get spelling suggestions.

Best
Erick

On Fri, Feb 11, 2011 at 8:55 AM, Thumuluri, Sai
sai.thumul...@verizonwireless.com wrote:
 Good Morning,
 I have implemented Solr 1.4.1 in our UAT environment