Skip to content
This repository has been archived by the owner on May 25, 2021. It is now read-only.

Let "error" replication document updates bypass the VDU function. #50

Merged
merged 1 commit into from
Oct 14, 2016

Conversation

nickva
Copy link
Contributor

@nickva nickva commented Oct 14, 2016

This is necessary in the case where an software upgrade happens with
a more restrictive VDU function. Replicator db might end up having documents
which would not pass validation anymore, leading to a replicator manager
crash when it updates the document with an "error" state.

So in case of an "error" state allow malformed document so the user can
see the error.

COUCHDB-3199

This is necessary in the case where an software upgrade happens with
a more restrictive VDU function. Replicator db might end up having documents
which would not pass validation anymore, leading to a replicator manager
crash when it updates the document with an "error" state.

So in case of an "error" state allow malformed document so the user can
see the error.

COUCHDB-3199
@rnewson
Copy link
Member

rnewson commented Oct 14, 2016

+1

@asfgit asfgit merged commit 48996b1 into apache:master Oct 14, 2016
@nickva nickva deleted the couchdb-3199 branch October 14, 2016 19:25
asfgit pushed a commit that referenced this pull request Mar 14, 2017
Use do_checkpoint instead of do_last_checkpoint, as last checkpoint variant
assumes there are more sequences in progress, which might not be true for
continuous replications.

(It also looks cleaner as don't have to handle gen_server results)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants