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

Andy Webb updated SOLR-17959:
-----------------------------
    Description: 
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/3802 adds an alwaysStopwords option that 
disables the default behaviour, enabling stopwords to be always ignored.

  was:
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.


> 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/3802 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to