[
https://issues.apache.org/jira/browse/SOLR-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851645#comment-13851645
]
Markus Jelsma commented on SOLR-3085:
-------------------------------------
I think that would be certainly better than the current situation. But there
may be another issue; if you don't remove stopwords at all, like we do, there
is a problem with mm and stop words too. For example: q=train from amsterdam to
rotterdam&mm=2<-1 5<80%; ideally you would not want documents with only terms
`from`, `to` and another non-stop word to match. In this case we would need mm
to apply only on non-stop words but also need a query time stopwordfilter that
doesn't remove them but marks them as stop words.
> 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
> Labels: MinimumShouldMatch, dismax, stopwords
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
