[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lucene-dev
Subject:    [jira] [Commented] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
From:       Jan_Høydahl_(JIRA) <jira () apache ! org>
Date:       2016-05-31 20:50:12
Message-ID: JIRA.12974063.1464654620000.342016.1464727812902 () Atlassian ! JIRA
[Download RAW message or body]


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

Jan Høydahl commented on SOLR-9174:
-----------------------------------

As long as you set mm, you should not need to set q.op. But there seems to be a bug \
leading to q.op=AND overriding mm in some cases, so just try your particular use case \
with q.op=OR and report back your findings. I'm afraid you may end up with other \
queries not working the way you intended with q.op=OR :(

> 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


[prev in list] [next in list] [prev in thread] [next in thread]