[jira] [Commented] (SOLR-2649) MM ignored in edismax queries with operators

["Mikołaj Kania (JIRA)" <ji...@apache.org>]

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

Mikołaj Kania commented on SOLR-2649:
-------------------------------------

We have lately encountered a problem with the current edismax behaviour, when {code}((x y z) AND (a)){code} gave the same results as {code}((x or y or z) and (a)){code} instead of {code}(a and b and c and d){code}. Our mm was set to 100% so it was really unexpected! What's more, {code} x y z{code} is the same as {code}x AND y AND z{code} and as {code}x AND y z{code}, so the behaviour is experience-driven, nondeterministic. It would be nice to see patches applied as the issue is now the most upvoted, open task.

> 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
>            Assignee: Erick Erickson
>            Priority: Minor
>             Fix For: 4.9, Trunk
>
>         Attachments: SOLR-2649-with-Qop.patch, SOLR-2649-with-Qop.patch, SOLR-2649.diff, SOLR-2649.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org