[sraggio]

1 year, 10 months ago #31565

We discovered an issue when searching for the last name of a musician (Butting) on our site. We have nothing in stock for this musician, so there should be zero results, but instead there are 56:
https://www.broinc.com/media?s=butting
His name does not appear anywhere in the results page.
I thought this might be an issue with the “ing” at the end being treated as part of the root word “Butt”, however a search for “Butt” (https://www.broinc.com/media?s=butt) correctly shows the 18 items available for that musician. None of those 18 are included in the 56 results for “Butting”. Any idea what might be going on here? Both partial and fuzzy options in section 2 of the plugin are off/inactive.

[wpsolr]

1 year, 10 months ago #31566

You have the exact same results for https://www.broinc.com/media?s=butting and https://www.broinc.com/media?s=but

I think “butting” is stemmed to “but”, which should be a stop word.

[sraggio]

1 year, 10 months ago #31567

Ah, that makes sense. Is it possible to edit the stopwords list?
Wrapping the search term in quotes to search for an exact match does not have any effect; I thought I saw something in this forum about adding that option as a feature, is that planned for a future release?

[wpsolr]

1 year, 10 months ago #31568

Each search engine has its own way of dealing with stop words.

– Apache Solr: https://solr.apache.org/guide/solr/latest/indexing-guide/filters.html#stop-filter
– Elasticsearch: https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-stop-analyzer.html

For engines with full or hybrid AI capabilities (Weaviate, Google Retail, Algolia), this should not be so important, as results should be based on the meaning of keywords rather than on keywords themselves.