and to say anything about your particular situation we need to see the field definitions from the schema for the field you expect stopwrods to be removed from and the stopwords file for those fields.
But Walter’s comment is germane. Stopwords lead to a number of incongruities and are best just left in. Best, Erick > On Mar 28, 2019, at 8:05 AM, Walter Underwood <wun...@wunderwood.org> wrote: > > Why are you removing stopwords? That hack made sense in the 1950s, but I > haven’t removed stopwords for the last twenty years. > > wunder > Walter Underwood > wun...@wunderwood.org > http://observer.wunderwood.org/ (my blog) > >> On Mar 28, 2019, at 2:47 AM, Ashish Bisht <bishtashis...@gmail.com> wrote: >> >> Hi, >> >> We are trying to remove stopwords from analysis using edismax parser >> parameter.The documentation says >> >> *stopwords >> A Boolean parameter indicating if the StopFilterFactory configured in the >> query analyzer should be respected when parsing the query. If this is set to >> false, then the StopFilterFactory in the query analyzer is ignored.* >> >> https://lucene.apache.org/solr/guide/7_3/the-extended-dismax-query-parser.html >> >> >> But seems like its not working. >> >> http://Box-1:8983/solr/SalesCentralDev_4/select?q=internet of >> things&rows=0&defType=edismax&qf=search_field >> content*&stopwords=false*&debug=true >> >> >> "parsedquery":"+(DisjunctionMaxQuery((content:internet | >> search_field:internet)) DisjunctionMaxQuery((content:thing | >> search_field:thing)))", >> * "parsedquery_toString":"+((content:internet | search_field:internet) >> (content:thing | search_field:thing))",* >> >> >> Are we missing something here? >> >> >> >> -- >> Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html >
