[
https://issues.apache.org/jira/browse/SOLR-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471290#comment-13471290
]
Michael Krkoska commented on SOLR-3740:
---------------------------------------
bq. In this specific case, you may want autoGeneratePhraseQueries="true" set on
your field type so that any split tokens end up acting like a phrase query of
"ID 100".
Thanks, that's indeed useful! But while it is a workaround for some cases of
the bug, I still see the issue as something serious.
> ExtendedDismaxQParser (edismax) does not obey q.op for parenthesized
> sub-queries
> --------------------------------------------------------------------------------
>
> Key: SOLR-3740
> URL: https://issues.apache.org/jira/browse/SOLR-3740
> Project: Solr
> Issue Type: Bug
> Components: query parsers
> Affects Versions: 3.6.1, 4.0-BETA
> Reporter: Jack Krupansky
>
> For a query such as "cat dog (fox bat fish)" with &q.op=AND, the default
> query operator is only set to AND for the top-level query, and not for the
> parenthesize sub-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 and never sets
> the default query operator when it invokes the classic Lucene Query parser
> which in turn is performing parsing and query generation for the
> parenthesized sub-query.
> 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
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
