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

Shawn Heisey commented on SOLR-2649:
------------------------------------

bq. Thank you! We have been waiting a long time for this fix.

I'm a little confused here.  Were you talking to me?  I don't have a fix, I was 
just saying that I'm having the same problem, and that my problem is not 
exactly like the initial description.  The initial description says that when 
boolean operators are present, edismax behaves as if mm=100%.  I'm seeing the 
opposite.

To summarize: When boolean operators are present in the query, two versions of 
Solr are behaving as if I did not have mm=100%, q.op=AND, or 
defaultOperator=AND in the schema.  Both versions behave as if the default 
operator is OR.  For 3.5, I have tried all three of those options 
simultaneously.  For 4.1, I have tried just the first two, because 
defaultOperator is deprecated.

                
> MM ignored in edismax queries with operators
> --------------------------------------------
>
>                 Key: SOLR-2649
>                 URL: https://issues.apache.org/jira/browse/SOLR-2649
>             Project: Solr
>          Issue Type: Bug
>          Components: query parsers
>            Reporter: Magnus Bergmark
>            Priority: Minor
>             Fix For: 4.2, 5.0
>
>
> Hypothetical scenario:
>   1. User searches for "stocks oil gold" with MM set to "50%"
>   2. User adds "-stockings" to the query: "stocks oil gold -stockings"
>   3. User gets no hits since MM was ignored and all terms where AND-ed 
> together
> The behavior seems to be intentional, although the reason why is never 
> explained:
>   // For correct lucene queries, turn off mm processing if there
>   // were explicit operators (except for AND).
>   boolean doMinMatched = (numOR + numNOT + numPluses + numMinuses) == 0; 
> (lines 232-234 taken from 
> tags/lucene_solr_3_3/solr/src/java/org/apache/solr/search/ExtendedDismaxQParserPlugin.java)
> This makes edismax unsuitable as an replacement to dismax; mm is one of the 
> primary features of dismax.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Reply via email to