lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naomi Dushay (JIRA)" <>
Subject [jira] [Commented] (SOLR-3589) Edismax parser does not honor mm parameter if analyzer splits a token
Date Thu, 13 Sep 2012 01:00:09 GMT


Naomi Dushay commented on SOLR-3589:

I may have stumbled into something.   Try setting q.op explicitly.


gives me a lot more results than


oddly,   q.op=OR   gives me the same results as setting it to AND.

Why did I stumble into this?


"In Solr 1.4 and prior, you should basically set mm=0 if you want the equivilent of q.op=OR,
and mm=100% if you want the equivilent of q.op=AND. In 3.x and trunk the default value of
mm is dictated by the q.op param (q.op=AND => mm=100%; q.op=OR => mm=0%). Keep in mind
the default operator is effected by your schema.xml <solrQueryParser defaultOperator="xxx"/>
entry. In older versions of Solr the default value is 100% (all clauses must match)"

I have q.op set in my schema, thus:

<solrQueryParser defaultOperator="AND" />

but when I use the q.op parameter, I experience something different.  Wild! 

Does this give us any insights?
> Edismax parser does not honor mm parameter if analyzer splits a token
> ---------------------------------------------------------------------
>                 Key: SOLR-3589
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 3.6, 4.0-BETA
>            Reporter: Tom Burton-West
>         Attachments: testSolr3589.xml.gz, testSolr3589.xml.gz
> With edismax mm set to 100%  if one of the tokens is split into two tokens by the analyzer
chain (i.e. "fire-fly"  => fire fly), the mm parameter is ignored and the equivalent of
 OR query for "fire OR fly" is produced.
> This is particularly a problem for languages that do not use white space to separate
words such as Chinese or Japenese.
> See these messages for more discussion:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

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

View raw message