[
https://issues.apache.org/jira/browse/SOLR-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
alexey updated SOLR-1384:
-------------------------
Attachment: SOLR-1384.patch
Please consider new patch. MinShouldMatch parameter value moved to
SolrQueryParser according to Hoss Man's comment.
> 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, 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]
