[
https://issues.apache.org/jira/browse/SOLR-17998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18041974#comment-18041974
]
ASF subversion and git services commented on SOLR-17998:
--------------------------------------------------------
Commit f0732fd157c0dcbc6f6cb3f1a61b2df2864b9248 in solr's branch
refs/heads/branch_10x from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=f0732fd157c ]
SOLR-17998: Improve error response, and RemoteSolrException (#1657)
This is true for the v1 and v2 API. Various SolrException classes have been
refactored to be more streamlined.
JSON lists are (once again) indented if they are larger than 1 element.
(cherry picked from commit 70c586f96d14cc724696172f6adb9057d4e77a6e)
> Improve Error Response and RemoteSolrException
> ----------------------------------------------
>
> Key: SOLR-17998
> URL: https://issues.apache.org/jira/browse/SOLR-17998
> Project: Solr
> Issue Type: Improvement
> Reporter: Houston Putman
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently error responses try to shove a full stack trace into whatever
> format the user has requested. This is really hard to use constructively
> since the stack trace is no longer formatted as it should be. Instead, we
> should have a structured error response output that can then be more easily
> read.
> Another benefit of this is that the RemoteSolrException can use this
> structured error output to give more information to SolrJ clients about what
> the ultimate source of their error is.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
