[
https://issues.apache.org/jira/browse/SOLR-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15038355#comment-15038355
]
Erick Erickson commented on SOLR-2649:
--------------------------------------
[[email protected]] [~janhoy] [~hossman] [~rmuir] [~dsmiley] [~chrism]
Picking random names that have committed stuff to this file if any of you care
to comment:
I'm running precommit and tests on this at present, but it makes me nervous
that the comment around line ExtendedDismaxQParser[347] in current trunk
// For correct lucene queries, turn off mm processing if there
// were explicit operators (except for AND).
has been in ExtendedDismaxQParser since it was first committed, and this is the
bit that's being re-worked.
I'm not sure about committing this at all, I'm just gathering information about
the current state of the patch at this point. That said, this seems reasonable.
But I confess the intricacies of all this stuff are not something I understand
very well...
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]