couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shorin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-2538) GET /db/doc?open_revs={} produces unsual response in CouchDB 2.0
Date Fri, 09 Jan 2015 15:09:35 GMT

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

Alexander Shorin commented on COUCHDB-2538:
-------------------------------------------

Not sure what where the reasons for such change during Stack Hash implementation: https://github.com/apache/couchdb-chttpd/commit/0592297776fa700134b0d283a5f3c512f0f96533#diff-e5123f75012e2b3a7edc96b2f0a863b0R524
/cc [~kocolosk]

Should we revert this to match httpd behaviour? I think we should or change httpd vice versa.



> GET /db/doc?open_revs={} produces unsual response in CouchDB 2.0
> ----------------------------------------------------------------
>
>                 Key: COUCHDB-2538
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2538
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Database Core
>            Reporter: Glynn Bird
>
> In CouchDB 1.6, if you call
> /db/doc?open_revs={}, (i.e. an invalid open_revs parameter) the following response arrives:
> {Code}
> {
> error: "unknown_error",
> reason: "function_clause"
> }
> {Code}
> but in CouchDB 2.0, we get the following response:
> {Code}
> {
> error: "function_clause",
> reason: null,
> ref: 2708187554
> }
> {Code}
> * the error message is different
> * the 'reason' field as switched to the 'error' field
> This was spotted by going through the breaking PouchDB automated tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message