lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-11631) Schema API always has status 0
Date Tue, 09 Jan 2018 22:53:00 GMT

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

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

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

SOLR-11631: fix another test


> 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
>            Assignee: Steve Rowe
>             Fix For: master (8.0), 7.3
>
>         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


Mime
View raw message