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 Fri, 17 Aug 2012 00:45:38 GMT


Jack Krupansky commented on SOLR-3589:

I could back off and simply say that edismax should set the Lucene default query operator
to "AND" if "q.op" is "AND", but that would not address this particular issue, which is complaining
that mm won't force the split terms to be ANDed.

If we really want to say that mm CAN'T be used to force split terms to be ANDED, then we should
really resolve this issue asinvalid/won't fix.

I should probably file a separate issue for the fact that q.op is not obeyed for any but the
top-level query.

And, the wiki makes no mention of "mm" being intended only for the top level query.

> 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