[
https://issues.apache.org/jira/browse/SOLR-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643428#comment-14643428
]
David Smiley commented on SOLR-3085:
------------------------------------
[~simon.endele] Yes it would. So would the solution of converting these
clauses to boost queries, which I did some months ago as part of a custom
client-specific query parser, and it works fine.
One reason I like converting these clauses to boost queries is that from a
Lucene internals/performance perspective, we separate out the clauses we know
aren't a must-match into the boost, which is in a SHOULD position, and is thus
secondary since the docs in the boost can be skipped past for docs that don't
stand a chance. I believe this is faster than one BooleanQuery with a smaller
min-should-match.
Jan's patch for mm.autoRelax looks good to me. I suggest another name however,
one involving "stopwords". Perhaps "mm.discountStopwords".
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
