You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2018/04/09 04:39:00 UTC

[jira] [Commented] (SOLR-3741) ExtendedDismaxQParser (edismax) does not obey q.op for queries with operators

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

Erick Erickson commented on SOLR-3741:
--------------------------------------

Can this be closed? There's been a lot of changes since this was opened.

> ExtendedDismaxQParser (edismax) does not obey q.op for queries with operators
> -----------------------------------------------------------------------------
>
>                 Key: SOLR-3741
>                 URL: https://issues.apache.org/jira/browse/SOLR-3741
>             Project: Solr
>          Issue Type: Bug
>          Components: query parsers
>    Affects Versions: 3.6.1, 4.0-BETA
>            Reporter: Jack Krupansky
>            Priority: Major
>
> For a query such as "cat dog OR (fox bat fish)" with &q.op=AND, the default query operator remains "OR" for the entire query. This is not documented behavior and rather surprising.
> This happens because edismax only simulates the default operator by forcing "mm" (minMatch) to 100% for the top-level BooleanQuery alone, but only if there are NO explicit operators present.
> One solution is for edismax to always set the default query operator when calling the classic Lucene query parser, or at least when q.op=AND.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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