[
https://issues.apache.org/jira/browse/SOLR-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ryan closed SOLR-3496.
------------------------------
Resolution: Cannot Reproduce
This must have been fixed sometime in 4.x. Works fine in 4.9.0.
> Query parser exceptions no longer displayed in response - just displays "null"
> ------------------------------------------------------------------------------
>
> Key: SOLR-3496
> URL: https://issues.apache.org/jira/browse/SOLR-3496
> Project: Solr
> Issue Type: Bug
> Affects Versions: 3.6
> Reporter: Michael Ryan
> Priority: Minor
>
> Prior to 3.6, if you did a query like this:
> {noformat}http://localhost:8983/solr/select?q=AND{noformat}
> ...you would get an exception and stacktrace in the response like this:
> {noformat}Problem accessing /solr/select. Reason:
> org.apache.lucene.queryParser.ParseException: Cannot parse 'AND'....{noformat}
> In 3.6, you get something like this:
> {noformat}Problem accessing /solr/select. Reason:
> null{noformat}
> I think the old behavior was preferable :)
> It looks like this was broken by SOLR-3022. Quick fix I think would be to
> change this:
> {code} public SolrException(ErrorCode code, Throwable th) {
> this(code, null, th, (th instanceof SolrException) ?
> ((SolrException)th).logged : false);
> }{code}
> To this:
> {code} public SolrException(ErrorCode code, Throwable th) {
> this(code, th.toString(), th, (th instanceof SolrException) ?
> ((SolrException)th).logged : false);
> }{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
