[
https://issues.apache.org/jira/browse/SOLR-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411542#comment-13411542
]
Yonik Seeley commented on SOLR-3377:
------------------------------------
I took a quick look at the current edismax code.
The major flaw seems to be the attempt to check user fields in
splitIntoClauses(). That method was never meant to be an exact replication of
Lucene query parsing. Is there a reason we aren't checking user fields in the
parser itself (the ExtendedSolrQueryParser.getFieldQuery)?
> eDismax: A fielded query wrapped by parens is not recognized
> ------------------------------------------------------------
>
> Key: SOLR-3377
> URL: https://issues.apache.org/jira/browse/SOLR-3377
> Project: Solr
> Issue Type: Bug
> Components: query parsers
> Affects Versions: 3.6
> Reporter: Jan Høydahl
> Priority: Critical
> Fix For: 4.0, 3.6.1
>
> Attachments: SOLR-3377.patch, SOLR-3377.patch, SOLR-3377.patch,
> SOLR-3377.patch
>
>
> As reported by "bernd" on the user list, a query like this
> {{q=(name:test)}}
> will yield 0 hits in 3.6 while it worked in 3.5. It works without the parens.
--
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
