[
https://issues.apache.org/jira/browse/SOLR-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Preetam Rao updated SOLR-1384:
------------------------------
Description:
Dis max query provides "mm" parameter that can be set on the underlying Lucene
Boolean OR query using setMinMustMatch() method.
It will be great if we can have the same support on any fq 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
was:
Dis max query provides "mm" parameter that can be set on the underlying Lucene
Boolean OR query using setMinMustMatch() method.
It will be great if we can have the same support on any fq 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
> Allow fqs 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.5
> Reporter: Preetam Rao
> Priority: Minor
> Fix For: 1.5
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Dis max query provides "mm" parameter that can be set on the underlying
> Lucene Boolean OR query using setMinMustMatch() method.
> It will be great if we can have the same support on any fq 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
