Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Message-ID: <210114289.1259016999738.JavaMail.jira@brutus>
Date: Mon, 23 Nov 2009 22:56:39 +0000 (UTC)
From: "Paul R. Brown (JIRA)" <jira@apache.org>
To: solr-dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-1576) Provide better error reporting for
 clients performing updates (or other operations)
In-Reply-To: <54826936.1258617459745.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781688#action_12781688 ] 

Paul R. Brown commented on SOLR-1576:
-------------------------------------

I ended up dealing with this particular item by implementing a custom update processor that puts a block with the document id and a messge into the response when an update fails.

> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.