couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1906) Removing DB referenced by _replicator should halt replication / remove doc
Date Thu, 10 Oct 2013 19:55:42 GMT

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

Robert Newson commented on COUCHDB-1906:
----------------------------------------

The document should transition to an error state given that the target db is missing or to
a success state if created with create_target:true.

The replication is *not* cancelled or halted so that would be inappropriate too.

What if someone deletes the target db specifically to get it repopulated from scratch via
the replication job? It's unreasonable to conflate the two things.


> Removing DB referenced by _replicator should halt replication / remove doc 
> ---------------------------------------------------------------------------
>
>                 Key: COUCHDB-1906
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1906
>             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
(v6.1#6144)

Mime
View raw message