[ 
https://issues.apache.org/jira/browse/SOLR-16004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819490#comment-17819490
 ] 

Mikhail Khludnev commented on SOLR-16004:
-----------------------------------------

Quite interesting alternative to SOLR-17101. Note dismax  calls this param as 
{{mm}} already.  

> Add support for minShouldMatch and tolerateOtherTerms in {!terms} 
> TermsQParserPlugin
> ------------------------------------------------------------------------------------
>
>                 Key: SOLR-16004
>                 URL: https://issues.apache.org/jira/browse/SOLR-16004
>             Project: Solr
>          Issue Type: Improvement
>          Components: query parsers
>    Affects Versions: main (10.0)
>            Reporter: Michael Gibney
>            Priority: Minor
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> In Solr, the TermsQParser considers a match if _any_ term in a doc/field 
> matches. It can be useful in some contexts (e.g., access control, etc.) to 
> require that a certain threshold of terms match, or to require exclusive 
> presence of enumerated terms (i.e., place a limit on the number of terms that 
> exist in a document that have _not_ been explicitly enumerated in the query).
> As a point of comparison, Elasticsearch implements the former feature as the 
> [minimum_should_match_field 
> param|https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-terms-set-query.html#terms-set-field-params]
>  on its "Terms set query" (the latter feature -- exclusive presence -- is 
> afaict not implemented).



--
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