And if you want an absolutely beautiful example, try searching for this blog post:
https://lucidworks.com/blog/2011/12/28/why-not-and-or-and-not/ Best, Erick On Fri, May 27, 2016 at 8:23 AM, Walter Underwood <wun...@wunderwood.org> wrote: > If “llc” is a stopword, it is not in the index and can never be searched. > Period. > > I never use stopwords. They cause odd problems, like not being able to search > for “vitamin a”. > > When I was at Netflix, I discovered that the movie title “Being There” had > zero tokens after stemming and stopwording. Oops. So I poked around and found > ten more like that. > > https://observer.wunderwood.org/2007/05/31/do-all-stopword-queries-matter/ > <https://observer.wunderwood.org/2007/05/31/do-all-stopword-queries-matter/> > > wunder > Walter Underwood > wun...@wunderwood.org > http://observer.wunderwood.org/ (my blog) > > >> On May 27, 2016, at 4:49 AM, Preeti Bhat <preeti.b...@shoregrp.com> wrote: >> >> Hi, >> >> I was firing both leading and trailing queries. And the tollc is an example >> where we have llc which is stopword for me but needs to be retrieved during >> search. >> >> >> Thanks and Regards, >> Preeti Bhat >> >> -----Original Message----- >> From: Ahmet Arslan [mailto:iori...@yahoo.com.INVALID] >> Sent: Thursday, May 26, 2016 10:11 PM >> To: solr-user@lucene.apache.org; sandhus...@gmail.com >> Subject: Re: how can we use multi term search along with stop words >> >> Hi, >> >> Are you firing both trailing and leading wildcard query? >> Or you just put stars for emphasizing purposes? >> >> Please consider using normal queries, since you are already using a >> tokenized field. >> >> By the way what is 'tollc soon'? >> >> Ahmet >> >> >> >> On Thursday, May 26, 2016 4:33 PM, Preeti Bhat <preeti.b...@shoregrp.com> >> wrote: >> Hi Ahmet & Sid, >> >> Thanks for the reply >> >> I have the below requirement >> 1) If I search with say company_nm:*llc* then we should not return any >> results or only few results where llc is embedded in other words like tollc >> soon. So I had implemented the stopwords. >> 2) But If I search with say company_nm:*google llc* then it should return >> the result of google llc and soon. >> >> The problem here is 1st part is working perfectly, while the second part is >> not working. >> >> >> Thanks and Regards, >> Preeti Bhat >> Shore Group Associates LLC >> (C) +91-996-644-8187 >> www.ShoreGroupAssociates.com >> >> -----Original Message----- >> From: Siddhartha Singh Sandhu [mailto:sandhus...@gmail.com] >> Sent: Thursday, May 26, 2016 6:54 PM >> To: solr-user@lucene.apache.org; Ahmet Arslan >> Subject: Re: how can we use multi term search along with stop words >> >> Hi Preeti, >> >> You can use the analysis tool in the Solr console to see how your queries >> are being tokenized. Based on your results you might need to make changes in >> "strings_ci". >> >> Also, If you want to be able to search on stopwords you might want to remove >> solr.StopFilterFactory from indexing and query analyzer of "strings_ci". The >> stopwords.txt is present in the core conf directory. You will need to >> re-index after you make these changes. >> >> Regards, >> >> Sid. >> >> >> On Thu, May 26, 2016 at 7:26 AM, Ahmet Arslan <iori...@yahoo.com.invalid> >> wrote: >> >>> Hi Bhat, >>> >>> What do you mean by multi term search? >>> In your first e-mail, your example uses quotes, which means >>> phrase/proximity search. >>> >>> ahmet >>> >>> >>> >>> On Thursday, May 26, 2016 11:49 AM, Preeti Bhat >>> <preeti.b...@shoregrp.com> >>> wrote: >>> HI All, >>> >>> Sorry for asking the same question again, but could someone please >>> advise me on this. >>> >>> >>> Thanks and Regards, >>> Preeti Bhat >>> >>> >>> From: Preeti Bhat >>> Sent: Wednesday, May 25, 2016 2:22 PM >>> To: solr-user@lucene.apache.org >>> Subject: how can we use multi term search along with stop words >>> >>> HI, >>> >>> I am trying to search the field named company_nm with value "Google llc". >>> We have the stopword on "llc", so when I try to search it returns 0 >>> results. Could anyone please guide me through the process of using >>> stopwords in multi term search. >>> >>> Please note I am using solr 6.0.0 and using standard parser. >>> >>> <fieldType name="string_ci" class="solr.TextField"> >>> <analyzer type="index"> >>> <tokenizer class="solr.StandardTokenizerFactory"/> >>> <filter class="solr.LowerCaseFilterFactory"/> >>> <filter class="solr.StopFilterFactory" >>> words="stopwords.txt" ignoreCase="true"/> >>> </analyzer> >>> <analyzer type="query"> >>> <tokenizer class="solr.StandardTokenizerFactory"/> >>> <filter class="solr.LowerCaseFilterFactory"/> >>> <filter class="solr.StopFilterFactory" >>> words="stopwords.txt" ignoreCase="true"/> >>> </analyzer> >>> <!-- No analysis at all when doing queries that involved Multi-Term >>> expansion --> >>> <analyzer type="multiterm"> >>> <tokenizer class="solr.KeywordTokenizerFactory" /> >>> </analyzer> >>> </fieldType> >>> <field name="company_nm" type="string_ci" indexed="true" >>> stored="true"/> >>> >>> >>> Thanks and Regards, >>> Preeti Bhat >>> >>> >>> >>> NOTICE TO RECIPIENTS: This communication may contain confidential >>> and/or privileged information. If you are not the intended recipient >>> (or have received this communication in error) please notify the >>> sender and it-supp...@shoregrp.com immediately, and destroy this >>> communication. Any unauthorized copying, disclosure or distribution of >>> the material in this communication is strictly forbidden. Any views or >>> opinions presented in this email are solely those of the author and do >>> not necessarily represent those of the company. Finally, the recipient >>> should check this email and any attachments for the presence of >>> viruses. The company accepts no liability for any damage caused by any >>> virus transmitted by this email. >> >>> >> >> NOTICE TO RECIPIENTS: This communication may contain confidential and/or >> privileged information. If you are not the intended recipient (or have >> received this communication in error) please notify the sender and >> it-supp...@shoregrp.com immediately, and destroy this communication. Any >> unauthorized copying, disclosure or distribution of the material in this >> communication is strictly forbidden. Any views or opinions presented in this >> email are solely those of the author and do not necessarily represent those >> of the company. Finally, the recipient should check this email and any >> attachments for the presence of viruses. The company accepts no liability >> for any damage caused by any virus transmitted by this email. >> >> NOTICE TO RECIPIENTS: This communication may contain confidential and/or >> privileged information. If you are not the intended recipient (or have >> received this communication in error) please notify the sender and >> it-supp...@shoregrp.com immediately, and destroy this communication. Any >> unauthorized copying, disclosure or distribution of the material in this >> communication is strictly forbidden. Any views or opinions presented in this >> email are solely those of the author and do not necessarily represent those >> of the company. Finally, the recipient should check this email and any >> attachments for the presence of viruses. The company accepts no liability >> for any damage caused by any virus transmitted by this email. >> >> >
