[SOLR-3589] Edismax parser does not honor mm parameter if analyzer splits a token

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.6, 4.0-BETA
• Fix Version/s: 3.6.2, 4.1, 6.0
• Component/s: search
• Assignee: Robert Muir
• Reporter: Tom Burton-West
• Created: 02/Jul/12 16:51
• Updated: 09/May/16 18:48
• Resolved: 08/Nov/12 12:03

Description

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:
http://lucene.472066.n3.nabble.com/edismax-parser-ignores-mm-parameter-when-tokenizer-splits-tokens-hypenated-words-WDF-splitting-etc-tc3991911.html

http://lucene.472066.n3.nabble.com/edismax-parser-ignores-mm-parameter-when-tokenizer-splits-tokens-i-e-CJK-tc3991438.html

http://lucene.472066.n3.nabble.com/Why-won-t-dismax-create-multiple-DisjunctionMaxQueries-when-autoGeneratePhraseQueries-is-false-tc3992109.html

Issue Links

• is duplicated by: SOLR-3636 edismax, synonyms and mm=100%
• is related to: SOLR-3739 ExtendedDismaxQParser (edismax) does not obey q.op for tokens split by an analyzer
• is related to: SOLR-2368 Improve extended dismax (edismax) parser