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] [Commented] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
Date Tue, 07 Jun 2016 19:51:21 GMT

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

David Smiley commented on SOLR-9174:
------------------------------------

In Solr 5.4 and before, you could use edismax like so (example assumes the techproducts data):
http://localhost:8983/solr/techproducts/select?q=ipod+OR+(power+AND+nonexistentword)&wt=json&indent=true&debugQuery=true&defType=edismax&mm=2%3C-1&stopwords=true&lowercaseOperators=true

Notice that it is a query that shows that the user knows the search syntax.  And notice the
mm allows 1 word to be optional.

If you run that query in 5.5 and forward, you get nothing.

> 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