[
https://issues.apache.org/jira/browse/SOLR-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491922#comment-13491922
]
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: https://issues.apache.org/jira/browse/SOLR-3589
> 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:
> 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
--
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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
