couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Stevens (JIRA)" <>
Subject [jira] [Issue Comment Deleted] (COUCHDB-1906) Removing DB referenced by _replicator should halt replication / remove doc
Date Thu, 10 Oct 2013 19:55:46 GMT


Eli Stevens updated COUCHDB-1906:

    Comment: was deleted

(was: I think that viewpoint is overly focused on the implementation of how persistent replication
is accomplished, rather than what makes sense for the feature itself.  If document removal
specifically is an issue, perhaps the _replicator doc could be flagged as endpoint_removed
or similar.

Depending on replication topology it might be impossible for the entity doing the DB deletion
to know about all of the persistent replications involved, and even if it is possible, having
to perform N actions to cleanly remove a DB doesn't make sense to me when it could be done
with one.


> Removing DB referenced by _replicator should halt replication / remove doc 
> ---------------------------------------------------------------------------
>                 Key: COUCHDB-1906
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Replication
>            Reporter: Eli Stevens
> Removing a DB that is involved in replication via the _replicator DB should remove the
corresponding _replicator document.
> Currently, couch.log includes errors when the DB is removed.
> My perspective is that replication is "just a feature of a DB" in the same way that attachments
are; one doesn't need to separately remove attachments after deleting a DB, and similarly
I've already expressed that I'm no longer interested the DB, its attachments, its replications,
etc. by deleting it.

This message was sent by Atlassian JIRA

View raw message