You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2012/02/02 01:13:53 UTC
[jira] [Issue Comment Edited] (SOLR-3085) Fix the dismax/edismax
stopwords mm issue
[ https://issues.apache.org/jira/browse/SOLR-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198104#comment-13198104 ]
Hoss Man edited comment on SOLR-3085 at 2/2/12 12:12 AM:
---------------------------------------------------------
bq. So we get a required DisMax Query for alltags:the which does not match any docs.
I think you are missreading that output...
{code}
+( ( DisjunctionMaxQuery((alltags:the)~0.01)
DisjunctionMaxQuery((title_en:contract | alltags:contract)~0.01)
)~2
)
{code}
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".
was (Author: hossman):
bq. So we get a required DisMax Query for alltags:the which does not match any docs.
I think you are missreading that output...
{code{
+( ( DisjunctionMaxQuery((alltags:the)~0.01)
DisjunctionMaxQuery((title_en:contract | alltags:contract)~0.01)
)~2
)
{code}
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: https://issues.apache.org/jira/browse/SOLR-3085
> Project: Solr
> Issue Type: Bug
> Components: search
> Reporter: Jan Høydahl
> Labels: MinimumShouldMatch, dismax, stopwords
> Fix For: 3.6, 4.0
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org