[
https://issues.apache.org/jira/browse/SOLR-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438208#comment-13438208
]
Lance Norskog edited comment on SOLR-3741 at 8/21/12 8:16 AM:
--------------------------------------------------------------
Please post a unit test matrix demonstrating these rules. Not the code, just a
table/spreadsheet of inputs, parse trees, and outputs.
was (Author: lancenorskog):
Please post a unit test matrix demonstrating these rules.
> 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
> Fix For: 4.0, 3.6.2
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
