You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2016/12/22 15:16:58 UTC
[jira] [Commented] (SOLR-1576) Provide better error reporting for
clients performing updates (or other operations)
[ https://issues.apache.org/jira/browse/SOLR-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770258#comment-15770258 ]
Erick Erickson commented on SOLR-1576:
--------------------------------------
Ran across this randomly, can it be closed? [~hossman_lucene@fucit.org]
> Provide better error reporting for clients performing updates (or other operations)
> -----------------------------------------------------------------------------------
>
> Key: SOLR-1576
> URL: https://issues.apache.org/jira/browse/SOLR-1576
> Project: Solr
> Issue Type: Improvement
> Components: update
> Affects Versions: 1.4
> Reporter: Paul R. Brown
> Priority: Minor
>
> It's frustrating from a client point of view to perform an update and then get back a {{400}} with no additional information. Would it make sense to supply an HTTP header with information about the error? I was thinking something like:
> {code}X-SOLR-ERROR-MESSAGE: unknown field 'fooBarBaz'{code}
> This would snap right into {{SolrDispatchFilter}} in {{sendError}} at line 363:
> {code}res.addHeader("X-SOLR-ERROR-MESSAGE",ex.getMessage());{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org