lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Matheis (steffkes) (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3382) Finegrained error propagation (focus on multi-document updates)
Date Fri, 20 Apr 2012 08:52:45 GMT

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

Stefan Matheis (steffkes) commented on SOLR-3382:
-------------------------------------------------

Per, just one quick thought, regarding http://wiki.apache.org/solr/Per%20Steffensen/Update%20semantics#Status_line
:
Can we stick with default reason-phrases and put ours in {{X-Error-*}} -Headers? Otherwise
we have to put String-Operations in Place, if we want to output these informations in some
type of frontend
                
> Finegrained error propagation (focus on multi-document updates)
> ---------------------------------------------------------------
>
>                 Key: SOLR-3382
>                 URL: https://issues.apache.org/jira/browse/SOLR-3382
>             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
happened.
> - 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message