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

ASF GitHub Bot commented on SOLR-1384:
--------------------------------------

GitHub user timofal opened a pull request:

    https://github.com/apache/lucene-solr/pull/186

    SOLR-1384 minShouldMatch parameter is supported for boolean query

    Please consider adding min-should-match support to boolean query. We need 
it and can't switch to eDisMax because of it's restriction. (eDisMax stops 
min-should-match processing if it finds boolean operators in subqueries.)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/timofal/lucene-solr 
SOLR-1384-minShouldMatch-in-booleanQuery

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/lucene-solr/pull/186.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #186
    
----
commit 4b0c3cc7b43db581a6e663bd9ca67d2d267e2644
Author: Alexey Timofeev <[email protected]>
Date:   2017-04-13T15:07:56Z

    SOLR-1384 minShouldMatch parameter is supported for boolean query

----


> Allow fq or q to specify boolean query min must match like dismax's mm 
> parameter
> --------------------------------------------------------------------------------
>
>                 Key: SOLR-1384
>                 URL: https://issues.apache.org/jira/browse/SOLR-1384
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>    Affects Versions: 1.4
>            Reporter: Preetam Rao
>            Priority: Minor
>             Fix For: 4.9, 6.0
>
>         Attachments: SOLR-1384.patch
>
>
> Dis max query provides "mm" parameter that can be set on the underlying 
> Lucene Boolean OR query using setMinimumNumberShouldMatch()  method.
> It will be great if we can have the same support on any fq or q that 
> specifies more than one term. This means we don't need to switch to dis max 
> query just for this one use case.
> Example might look like this:
> fq={!minMustMatch=75%}street:"917 Z st NW Washington DC"
> Full supported syntax for the value allowed should be this:
> http://lucene.apache.org/solr/api/org/apache/solr/util/doc-files/min-should-match.html
> This is the underlying lucene facility:
> http://www.netlikon.de/docs/javadoc-lucene/lucene_1_9/org/apache/lucene/search/BooleanQuery.html#setMinimumNumberShouldMatch%28int%29



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to