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-2407) Database updates feed is broken
Date Sat, 25 Oct 2014 22:33:33 GMT

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

Alexander Shorin commented on COUCHDB-2407:
-------------------------------------------

[~rnewson] sorry, but what do you mean? {{/_db_updates}} cannot be created manually - it just
a service feed that notifies about database changes: created, deleted, updated etc. It's ok
to make a notification delay while operation rolls over the cluster, but it's not a reason
to report about missed database instead. Anyway, this issue is aggregation of current {{/_db_updates}}
behavior in comparison with CouchDB 1.x. I would happy to skip it as "unsupported" as like
{{/_stats}} is (CouchDB 2.0 also reports "database not found" for it), but according query
parameters handling looks like it is supported, but just doesn't works properly.

> Database updates feed is broken
> -------------------------------
>
>                 Key: COUCHDB-2407
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2407
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: HTTP Interface
>    Affects Versions: 2.0.0
>            Reporter: Alexander Shorin
>
> For current state of CouchDB 2.0 (not sure to which commit make a reference, just for
"today") it acts very inconsistent:
> {code}
> http --json http://localhost:15984/_db_updates
> HTTP/1.1 404 Object Not Found
> Cache-Control: must-revalidate
> Content-Length: 58
> Content-Type: application/json
> Date: Sat, 25 Oct 2014 13:42:25 GMT
> Server: CouchDB/40c5c85 (Erlang OTP/17)
> X-Couch-Request-ID: 27e8ab2a
> X-CouchDB-Body-Time: 0
> {
>     "error": "not_found", 
>     "reason": "Database does not exist."
> }
> {code}
> Ok, there is no such database. But wait:
> {code}
> http --json 'http://localhost:15984/_db_updates?feed=eventsource'
> HTTP/1.1 400 Bad Request
> Cache-Control: must-revalidate
> Content-Length: 88
> Content-Type: application/json
> Date: Sat, 25 Oct 2014 13:39:59 GMT
> Server: CouchDB/40c5c85 (Erlang OTP/17)
> X-Couch-Request-ID: 3a5ca656
> X-CouchDB-Body-Time: 0
> {
>     "error": "bad_request", 
>     "reason": "Supported `feed` types: normal, continuous, longpoll"
> }
> {code}
> The eventsource feed type is supported by CouchDB 1.x. Ok, let's try suggested continuous
one:
> {code}
> http --json 'http://localhost:15984/_db_updates?timeout=1000&heartbeat=false&feed=continuous'
> HTTP/1.1 400 Bad Request
> Cache-Control: must-revalidate
> Content-Length: 51
> Content-Type: application/json
> Date: Sat, 25 Oct 2014 13:50:59 GMT
> Server: CouchDB/40c5c85 (Erlang OTP/17)
> X-Couch-Request-ID: 6c560dc2
> X-CouchDB-Body-Time: 0
> {
>     "error": "bad_request", 
>     "reason": "invalid_integer"
> }
> {code}
> The same request is correct for CouchDB 1.x. 



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

Mime
View raw message