[ https://issues.apache.org/jira/browse/SOLR-11631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16317554#comment-16317554 ]
Steve Rowe edited comment on SOLR-11631 at 1/9/18 2:18 AM: ----------------------------------------------------------- Noble's patch, fixing up test failures due to differently formatted error messages. Precommit and all Solr tests succeed. Committing shortly. was (Author: steve_rowe): Patch fixing up test failures due to differently formatted error messages. Precommit and all Solr tests succeed. Committing shortly. > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org