[
https://issues.apache.org/jira/browse/SOLR-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853922#comment-13853922
]
Markus Jelsma commented on SOLR-3085:
-------------------------------------
Hi Jan - the SolrCore.java modification should be in the patch. Anyway, it
looks like this fix does what it advertises. The problem i reported above,
perhaps another issue, is still real. Environments without stopwords still have
a problem with mm. Consider your q=A horse in a stable. With mm=2 we get all
kinds of documents, usually all documents in the corpus (in and a). Ideally
this or another parameter would only require horse and stable.
> 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: query parsers
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Labels: MinimumShouldMatch, dismax, edismax, stopwords
> Fix For: 5.0, 4.7
>
> Attachments: SOLR-3085.patch, SOLR-3085.patch, SOLR-3085.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1.4#6159)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
