[
https://issues.apache.org/jira/browse/SOLR-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448742#comment-13448742
]
John Freier commented on SOLR-2649:
-----------------------------------
Hey folks. I ran across this issue after noticing thousands of odd seeming
result sets with good ol' v3.4. I don't know all of the deeper implications,
but I think Jack's summary and a couple others' comments would make the most
sense and are already what seem to be described in the current documentation
which states that the boolean operators in front of of various terms or phrases
define them to be specifically included or excluded, while the others are
classified as 'optional'. Then, in the documentation on minimum match, it
states that it is based the percentages etc off of the "optional" terms, so I
would expect the boolean-specified ones not to be considered and for the mm to
just be based off of whatever optionals there are.
I saw this was a recent discussion so thought I'd chip in but sorry if you've
already come to this conclusion and/or implemented it. Is this how the 4.0
Alpha is patched now or could anyone point me to any sort of temporary solution
to achieve this functionality? Thanks for your great work. - John
> 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.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]
