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

ASF subversion and git services commented on SOLR-6117:
-------------------------------------------------------

Commit c951578fcabfd5520f425156b0fa35f35811554d in lucene-solr's branch 
refs/heads/master from [~gerlowskija]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c951578 ]

SOLR-6117: Unify ReplicationHandler error handling

Prior to this commit, ReplicationHandler had a few inconsistencies
in how it reported errors:
  - Sometimes the 'status' field was used as an enum (e.g. 'success'
    v. 'failure'.  Elsewhere it is used to hold error messages.
  - Sometimes an explicit 'message' field was used, but often not.
  - Sometimes a stack trace was provided in place of an error message.

This commit tweaks the various error cases in ReplicationHandler to
report errors consistently.  'status' is always an enum-type value.  A
'message' field is provided for all errors, with an optional 'exception'
field.


> Replication command=fetchindex always return success.
> -----------------------------------------------------
>
>                 Key: SOLR-6117
>                 URL: https://issues.apache.org/jira/browse/SOLR-6117
>             Project: Solr
>          Issue Type: Bug
>          Components: replication (java)
>    Affects Versions: 4.6, 7.5
>            Reporter: Raintung Li
>            Assignee: Jason Gerlowski
>            Priority: Major
>         Attachments: SOLR-6117-master.patch, SOLR-6117.patch, 
> SOLR-6117.patch, SOLR-6117.patch, SOLR-6117.txt
>
>
> Replication API command=fetchindex do fetch the index. while occur the error, 
> still give success response. 
> API should return the right status, especially WAIT parameter is 
> true.(synchronous).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to