You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2014/07/08 23:32:10 UTC

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

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

Shawn Heisey edited comment on SOLR-2649 at 7/8/14 9:31 PM:
------------------------------------------------------------

We got bitten by this bug today.  Consider this filter query, constructed from multiple entry boxes on an advanced search form:

{code}
{!edismax}publish:(0) AND caption:(john lennon)
{code}

The mm value is 100%, but we get results as if mm were 0.

What we're going to do for a solution is create multiple fq parameters instead of combining with AND.



was (Author: elyograg):
We got bitten by this bug today.  Consider this filter query, constructed from multiple entry boxes on an advanced search form:

{!edismax}publish:(0) AND caption:(john lennon)

The mm value is 100%, but we get results as if mm were 0.

What we're going to do for a solution is create multiple fq parameters instead of combining with AND.


> 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.9, 5.0
>
>         Attachments: 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.2#6252)

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