lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SOLR-3085) Fix the dismax/edismax stopwords mm issue
Date Sun, 02 Aug 2015 22:42:05 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651244#comment-14651244
] 

Jan Høydahl commented on SOLR-3085:
-----------------------------------

Due to popular demand, I committed the {{mm.autoRelax}} logic to trunk only, for people to
play with. After some broader exposure there we can consider porting to 5.x.

The {{mergeStopwords}} idea is spun off into SOLR-7862.

> 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, edismax, stopwords
>             Fix For: Trunk
>
>         Attachments: SOLR-3085.patch, 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.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message