[
https://issues.apache.org/jira/browse/SOLR-17998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039713#comment-18039713
]
Houston Putman commented on SOLR-17998:
---------------------------------------
I have also taken the time to refactor some error classes, such as removing
`RemoteExecutionException` in favor of `RemoteSolrException` and giving
`APIBag.ExceptionWithErrObject` a real exception class
`SolrErrorWrappingException` that can give better structured information to
users downstream.
> 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
>
> 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]
