lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Burton-West (JIRA)" <>
Subject [jira] [Commented] (SOLR-3589) Edismax parser does not honor mm parameter if analyzer splits a token
Date Tue, 06 Nov 2012 22:58:12 GMT


Tom Burton-West commented on SOLR-3589:

I back-ported to 3.6 branch.  Forgot to change the name from SOLR-3589.patch, so the 6/Nov/12
patch is the 3.6 patch against yesterdays svn version of 3.6.

Main difference I saw between 3.6 and 4.0 is that Solr 4.0 uses DisMaxQParser.parseMinShouldMatch()
to set the default at 0% if q.op=OR and %100 if q.op =AND

I just kept the 3.6 behavior which uses 3.6 default of 100% (if mm is not set)

I'll test the 3.6 patch against a production index tomorrow.

> 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
>            Assignee: Robert Muir
>         Attachments: SOLR-3589.patch, SOLR-3589.patch, SOLR-3589.patch, SOLR-3589.patch,
SOLR-3589.patch, SOLR-3589_test.patch, 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