lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naomi Dushay (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-3589) Edismax parser does not honor mm parameter if analyzer splits a token
Date Thu, 13 Sep 2012 17:18:08 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454533#comment-13454533
] 

Naomi Dushay edited comment on SOLR-3589 at 9/14/12 4:17 AM:
-------------------------------------------------------------

(comment redacted! -- I can't repeat the results today.  Perhaps I was missing a Solr commit
... since the index is behaving differently, and I didn't change the index, though I did restart
Solr a few times.)

(below left for historical purposes)

I may have stumbled into something.   Try setting q.op explicitly.

(baseurl)/select?q=fire-fly

gives me a lot more results than

(baseurl)/select?q=fire-fly&q.op=AND


oddly,   q.op=OR   gives me the same results as setting it to AND.


Why did I stumble into this?

from http://wiki.apache.org/solr/DisMaxQParserPlugin#mm_.28Minimum_.27Should.27_Match.29

"In Solr 1.4 and prior, you should basically set mm=0 if you want the equivilent of q.op=OR,
and mm=100% if you want the equivilent of q.op=AND. In 3.x and trunk the default value of
mm is dictated by the q.op param (q.op=AND => mm=100%; q.op=OR => mm=0%). Keep in mind
the default operator is effected by your schema.xml <solrQueryParser defaultOperator="xxx"/>
entry. In older versions of Solr the default value is 100% (all clauses must match)"

I have q.op set in my schema, thus:

<solrQueryParser defaultOperator="AND" />

but when I use the q.op parameter, I experience something different.  Wild! 

Does this give us any insights?
                
      was (Author: ndushay):
    I may have stumbled into something.   Try setting q.op explicitly.

(baseurl)/select?q=fire-fly

gives me a lot more results than

(baseurl)/select?q=fire-fly&q.op=AND


oddly,   q.op=OR   gives me the same results as setting it to AND.


Why did I stumble into this?

from http://wiki.apache.org/solr/DisMaxQParserPlugin#mm_.28Minimum_.27Should.27_Match.29

"In Solr 1.4 and prior, you should basically set mm=0 if you want the equivilent of q.op=OR,
and mm=100% if you want the equivilent of q.op=AND. In 3.x and trunk the default value of
mm is dictated by the q.op param (q.op=AND => mm=100%; q.op=OR => mm=0%). Keep in mind
the default operator is effected by your schema.xml <solrQueryParser defaultOperator="xxx"/>
entry. In older versions of Solr the default value is 100% (all clauses must match)"

I have q.op set in my schema, thus:

<solrQueryParser defaultOperator="AND" />

but when I use the q.op parameter, I experience something different.  Wild! 

Does this give us any insights?
                  
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message