lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3085) Fix the dismax/edismax stopwords mm issue
Date Wed, 01 Feb 2012 20:09:02 GMT


Hoss Man commented on SOLR-3085:

bq. So we get a required DisMax Query for alltags:the which does not match any docs. 

I think you are missreading that output...

+( ( DisjunctionMaxQuery((alltags:the)~0.01) 
     DisjunctionMaxQuery((title_en:contract | alltags:contract)~0.01)

The "DisjunctionMaxQuery((alltags:the)~0.01)" clause is not required in that query.  it is
one of two SHOULD clauses in a boolean query, and becomes subject to the same "mm" rule. 
both clauses in that BooleanQuery are already SHOULD clauses, so i don't know what it would
mean to make then more "optional".

> Fix the dismax/edismax stopwords mm issue
> -----------------------------------------
>                 Key: SOLR-3085
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>            Reporter: Jan H√łydahl
>              Labels: MinimumShouldMatch, dismax, stopwords
>             Fix For: 3.6, 4.0
> As discussed here and here
and here 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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message