lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
Date Wed, 01 Jun 2016 21:36:59 GMT

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

David Smiley edited comment on SOLR-9174 at 6/1/16 9:36 PM:
------------------------------------------------------------

This is definitely broken.  The current situation is that you can only have *ONE OF*:
* default AND but let users explicitly put "OR".  No partial "mm" requirement.  To do this
>= 5.5, set q.op=AND and mm=0%.  (FWIW I kinda hate setting q.op or df as it effects *all*
filter queries, facet queries, etc. not just 'q')
* mm of something other than 0%.   To do this, set mm as desired; q.op won't matter.

I can't seem to have it both ways no matter what combo of parameters I use.  I could have
it both ways prior to 5.5 easily enough by, if I recall, setting mm=whatever and let q.op
default to OR.

bq. I understood that q.op overrides mm. Is my understanding mentioned above right?

No, the other way around.  At least I say this from my historical pre 5.5 perspective; 5.5
forward I dunno any more :-/


was (Author: dsmiley):
This is definitely broken.  The current situation is that you can only have *ONE OF*:
* default AND but let users explicitly put "OR".  No partial "mm" requirement.  To do this
>= 5.5, set q.op=AND and mm=0%.  (FWIW I kinda hate setting q.op or df as it effects *all*
filter queries, facet queries, etc. not just 'q')
* mm of something other than 0%.   To do this, set mm as desired; q.op won't matter.

I can't seem to have it both ways no matter what combo of parameters I use.  I could have
it both ways prior to 5.5 easily enough by, if I recall, setting mm=whatever and let q.op
default to OR.

bq. I understood that q.op overrides mm. Is my understanding mentioned above right?

No, the other way around.

> After Solr 5.5, mm parameter doesn't work properly
> --------------------------------------------------
>
>                 Key: SOLR-9174
>                 URL: https://issues.apache.org/jira/browse/SOLR-9174
>             Project: Solr
>          Issue Type: Bug
>          Components: query parsers, search
>    Affects Versions: 5.5, 6.0, 6.0.1
>            Reporter: Issei Nishigata
>
> “mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5.
> In Solr 5.4, mm parameter works expectedly with the following setting.
> [schema]
> {code:xml}
> <fieldType name="bi_gram" class="solr.TextField">
>   <analyzer>
>     <tokenizer class="solr.NGramTokenizerFactory" minGramSize="2" maxGramSize="2"/>
>   </analyzer>
> </fieldType>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax&q.op=AND&mm=2&q=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> [Solr 5.4]
> {code:xml}
> <response>
> ...
>   <lst name="params">
>     <str name="mm">2</str>
>     <str name="q">solar</str>
>     <str name="defType">edismax</str>
>     <str name="q.op">AND</str>
>   </lst>
> ...
> <result name="response" numFound="1" start="0">
>   <doc>
>     <str name="id">0</str>
>     <arr name="content">
>       <str>solr</str>
>     </arr>
>   </doc>
> </result>
> <lst name="debug">
>   <str name="rawquerystring">solar</str>
>   <str name="querystring">solar</str>
>   <str name="parsedquery">
>   (+DisjunctionMaxQuery((((text:so text:ol text:la text:ar)~2))))/no_coord
>   </str>
>   <str name="parsedquery_toString">+(((text:so text:ol text:la text:ar)~2))</str>
>   ...
> </response>
> {code}
> [Solr 6.0.1]
> {code:xml}
> <response>
> ...
>   <lst name="params">
>     <str name="mm">2</str>
>     <str name="q">solar</str>
>     <str name="defType">edismax</str>
>     <str name="q.op">AND</str>
>   </lst>
> ...
> <result name="response" numFound="0" start="0"/>
>   <lst name="debug">
>     <str name="rawquerystring">solar</str>
>     <str name="querystring">solar</str>
>     <str name="parsedquery">
>     (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar))))/no_coord
>     </str>
>     <str name="parsedquery_toString">+((+text:so +text:ol +text:la +text:ar))</str>
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after Solr 5.5).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message