lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Per Steffensen (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3382) Finegrained error propagation (focus on multi-document updates)
Date Fri, 20 Apr 2012 08:24:42 GMT


Per Steffensen commented on SOLR-3382:

We have created a solution to this while adding the update-features of "fail if intent is
to insert new document and document already exists", "fail if intent is to update existing
document and document does not exist or has been changed since loaded" etc. as described in
SOLR-3173, SOLR-3178 and on
Details about the solution to this SOLR-3382 is also to be found on
Reason for solving this SOLR-3382 at the same time as SOLR-3173 and SOLR-3178 is that "unique
key constraint"- and "versioning"-errors are not worth much if they cannot get properly propagated
to the client.

We hope to contribe this solutions within a few weeks, but please feel free to comment, help
shape etc., and we will make changes according to the wishes of the community. 
> Finegrained error propagation (focus on multi-document updates)
> ---------------------------------------------------------------
>                 Key: SOLR-3382
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: clients - java, Response Writers, update
>    Affects Versions: 3.5
>            Reporter: Per Steffensen
>            Assignee: Per Steffensen
>              Labels: client, documents, error, multiple, propagation, update
>             Fix For: 4.0
> Today when an error occurs on server side during the handling of a request, the handling
of the request will stop at the point when the error occured, and only a error-message (reason
part of HTTP status line) and error-code (HTTP response code) is pushed back to the sender
of the request.
> This can be improved in several ways
> - Reacting as a client on errors, solely based on a textual message and a HTTP response
code is hard. The error ought have some kind of type telling the client which kind of error
> - When handling multi-document updates the error might happen during the handling of
one of the documents - potentially not the first document and potentially not the last document.
> -- The client ought to get information about which documents where successfully updated
(the ones comming before the document creating the error).
> -- If the error updating a document is not due to a general problem, it could very well
be that some of the documents not yet handled at the time of the error (the documents comming
after the document creating the error), could be successfully updated - so why not try that.
> -- If continuing the updating of documents, even after one document-update resulted in
an error (as suggested above), the updating of some of those documents might also result in
an error. This leads to another improvement, namely being able to send information about more
than one error back to the client.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message