couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-2497) Deprecate /_replicate endpoint
Date Mon, 08 Dec 2014 15:24:12 GMT


Robert Newson commented on COUCHDB-2497:

I think you miss my point. "persistent":true in the request body to _replicate would cause
us to store that information in a database.

What _replicator is is a regular database that we monitor for changes. It was a cute idea,
but I've administered this idea in production for years and I absolutely hate it now.

> Deprecate /_replicate endpoint
> ------------------------------
>                 Key: COUCHDB-2497
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: HTTP Interface, Replication
>            Reporter: Alexander Shorin
> We have two similar API to run replications. How about to reduce them single one? We
cannot just return HTTP 301 on /_replicate to /_replicator for POST requests since in this
case user must confirm the request submission whatever that means. But we can just reroute
requests internally or try to use experimental [HTTP 308|]
to deal with it.
> The motivation is the simplification of replication tasks management, since it doesn't
simply to cancel active temporary replication as like as it could be done for persistent ones.
> Thoughts?

This message was sent by Atlassian JIRA

View raw message