[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324426#comment-15324426
]
David Smiley commented on SOLR-9174:
------------------------------------
bq. So I don't think you were "having it both ways"; rather, your explicit mm
spec was being ignored when you included explicit operators in queries against
Solr < 5.5.0.
That's much better said; yes. So if a user uses explicit operators, then I
think "mm" should be ignored. This was the case < 5.5.0 and it appears you
restored that today for 6.1. A better example may have been a "ipod AND power
AND nonexistentword" which should return nothing despite the 'mm'.
> 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: [email protected]
For additional commands, e-mail: [email protected]
