lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Krupansky (JIRA)" <>
Subject [jira] [Commented] (SOLR-3589) Edismax parser does not honor mm parameter if analyzer splits a token
Date Thu, 16 Aug 2012 12:15:38 GMT


Jack Krupansky commented on SOLR-3589:

bq. It's not just mm. You set q.op to AND and it does the same thing.

Joel, you're right. Upon closer inspection of the code, I see that the reason is that edismax
never sets the Lucene default operator directly. Instead, it sets the default value of "mm"
parameter to 100% if "q.op" is "AND", and set's BooleanQuery.minNrShouldMatch to the number
of optional terms. That is equivalent to setting the default Lucene query operator at the
top-level boolean level, but has no effect for terms that get split down at the analyzer level.
Oh well. Scratch that suggestion.

I think I'm back to wanting to suggest that edismax should actually set the Lucene-level default
query operator if "mm" is 100%. I think that would fix the original problem and allow the
user to choose whether to user "mm" or "q.op" to control AND/OR.

> 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
>            Reporter: Tom Burton-West
> 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:!default.jspa
For more information on JIRA, see:


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

View raw message