Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Wed, 1 Feb 2012 14:22:58 +0000 (UTC)
From: =?utf-8?Q?Jan_H=C3=B8ydahl_=28Commented=29_=28JIRA=29?=
 <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <354640447.2710.1328106178734.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1739815840.2706.1328105699048.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (SOLR-3085) Fix the dismax/edismax stopwords mm
 issue
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Jan H=C3=B8ydahl 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 tel=
l it that if any analyzers removed a term, then that term would become opti=
onal for any fields for which it remained?  I'm not sure what the developme=
nt effort would perhaps it would be a nice way to circumvent this problem i=
n a future release...

I like the suggestion. Would this be possible?

Take as example this parsed query (q=3Dthe contract&qf=3Dalltags title_en&m=
m=3D100%defType=3Dedismax)
{noformat}
+((DisjunctionMaxQuery((alltags:the)~0.01) DisjunctionMaxQuery((title_en:co=
ntract | 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 i=
t possible in the (e)DisMax code to detect this and make the first DisMax q=
uery optional?
               =20
> 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=C3=B8ydahl
>              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/RfAp82=
nSsla 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 acro=
ss all fields in your QF, or relax the MM to a lower percentag. Sometimes t=
hese 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 administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
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