[
https://issues.apache.org/jira/browse/SOLR-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198361#comment-13198361
]
Hoss Man commented on SOLR-3085:
--------------------------------
bq. Then, one way may be to subtract the MM count accordingly, so that in our
case above, when we detect that the DisMax clause for "the" does not contain
"title_en", we do mm=mm-1 which will give us an MM of 1 instead of 2 and we'll
get hits. This is probably the easiest solution.
that wouldn't make any sense ... in your example that would result in the query
matching every doc containing "alltags:the" (or "title_en:contract", or
"alltags:contract") which hardly seems like what the user is likely to expect
if they used mm=100% (with or w/o a "mm.sw=false" param)
bq. Another way would be to keep mm as is, and move the affected clause out of
the BooleanQuery and add it as a BoostQuery instead?
something like that might work .. but i haven't thought it through very hard
... i have a nagging feeling that there are non-stopword cases that would be
indistinguishable (to the parser) from this type of stopword case, and thus
would also trigger this logic undesirably, but i can't articulate what they
might be off the top of my head.
> Fix the dismax/edismax stopwords mm issue
> -----------------------------------------
>
> Key: SOLR-3085
> URL: https://issues.apache.org/jira/browse/SOLR-3085
> Project: Solr
> Issue Type: Bug
> Components: search
> Reporter: Jan Høydahl
> Labels: MinimumShouldMatch, dismax, stopwords
> Fix For: 3.6, 4.0
>
>
> As discussed here http://search-lucene.com/m/Wr7iz1a95jx and here
> http://search-lucene.com/m/Yne042qEyCq1 and here
> http://search-lucene.com/m/RfAp82nSsla DisMax has an issue with stopwords if
> not all fields used in QF have exactly same stopword lists.
> Typical solution is to not use stopwords or harmonize stopword lists across
> all fields in your QF, or relax the MM to a lower percentag. Sometimes these
> are not acceptable workarounds, and we should find a better solution.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
