[jira] [Commented] (SOLR-11631) Schema API always has status 0

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

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

Commit 34b30da60cc4b6f9ed0a528d470eb075871db6f7 in lucene-solr's branch refs/heads/branch_7x from [~steve_rowe]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=34b30da ]

SOLR-11631: The Schema API should return non-zero status when there are failures


> Schema API always has status 0
> ------------------------------
>
>                 Key: SOLR-11631
>                 URL: https://issues.apache.org/jira/browse/SOLR-11631
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Steve Rowe
>         Attachments: SOLR-11631.patch, SOLR-11631.patch, SOLR-11631.patch
>
>
> Schema API failures always return status=0.
> Consumers should be able to detect failure using normal mechanisms (i.e. status != 0) rather than having to parse the response for "errors".  Right now if I attempt to {{add-field}} an already existing field, I get:
> {noformat}
> {responseHeader={status=0,QTime=XXX},errors=[{add-field={name=YYY, ...}, errorMessages=[Field 'YYY' already exists.]}]}
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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