lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (Commented) (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SOLR-3085) Fix the dismax/edismax stopwords mm issue
Date Wed, 01 Feb 2012 14:22:58 GMT

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

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

In this thread http://search-lucene.com/m/Tzktd1a95jx James Dyer suggests:
bq. I do wonder...what if (e)dismax had a flag you could set that would tell it that if any
analyzers removed a term, then that term would become optional for any fields for which it
remained?  I'm not sure what the development effort would perhaps it would be a nice way to
circumvent this problem in a future release...

I like the suggestion. Would this be possible?

Take as example this parsed query (q=the contract&qf=alltags title_en&mm=100%defType=edismax)
{noformat}
+((DisjunctionMaxQuery((alltags:the)~0.01) DisjunctionMaxQuery((title_en:contract | alltags:contract)~0.01))~2)
{noformat}

The field "alltags" does not use stopwords, but "title_en" does. So we get a required DisMax
Query for alltags:the which does not match any docs. Is it possible in the (e)DisMax code
to detect this and make the first DisMax query 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


Mime
View raw message