[
https://issues.apache.org/jira/browse/SOLR-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437426#comment-13437426
]
Lance Norskog edited comment on SOLR-3589 at 8/24/12 1:57 PM:
--------------------------------------------------------------
[
See [SOLR-3636], it's the same problem space but with synonym expansion. If
"Monkeyhouse" expands to "monkey house", then a dismax or edismax query finds
words with either ("monkey" OR "house"). Must-match defaults to 100% so you
would expect this to mean "monkey" AND "house".
This seems to be a multi-part problem.
] retracted as per below. Yes, synonyms are another box'o'fun.
was (Author: lancenorskog):
See [SOLR-3636], it's the same problem space but with synonym expansion. If
"Monkeyhouse" expands to "monkey house", then a dismax or edismax query finds
words with either ("monkey" OR "house"). Must-match defaults to 100% so you
would expect this to mean "monkey" AND "house".
This seems to be a multi-part problem.
> 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
> Attachments: 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
