You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@solr.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/10/22 20:48:00 UTC

[jira] [Updated] (SOLR-17959) Add alwaysStopwords option to edismax

     [ https://issues.apache.org/jira/browse/SOLR-17959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated SOLR-17959:
----------------------------------
    Labels: pull-request-available  (was: )

> Add alwaysStopwords option to edismax
> -------------------------------------
>
>                 Key: SOLR-17959
>                 URL: https://issues.apache.org/jira/browse/SOLR-17959
>             Project: Solr
>          Issue Type: Improvement
>          Components: query parsers
>            Reporter: Andy Webb
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We were surprised by edismax's behaviour for pure-stopword queries, having expected that these would return zero results. Its 'If a query consists of all stopwords, such as "to be or not to be", then all words are required.' behaviour is the opposite to what we want as we're using query-time stopwords to prevent particular query terms matching, but there's no way to disable the behaviour other than using dismax instead, which may have other impacts.
> https://github.com/apache/solr/pull/2488 adds an alwaysStopwords option that disables the default behaviour, enabling stopwords to be always ignored.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org