nickva opened a new pull request, #6168: URL: https://github.com/apache/couchdb/pull/6168
Replicated revisions, which the target already has, may come in with various revision path lengths. This can easily happen if source endpoints have different revs_limits (see #6162). Previously, if the target had a VDU, updates went through `prep_and_validate_replicated_updates/5` which incorrectly dropped any revisions already in the tree as a no-op. However, those revision paths, even if the leafs were no-ops, could still patch-up or connect some existing revisions into a single revpath. To fix this, we have to let the revison paths only through to updater to do the revtree merge. We tag a document as a `revs_only` update (we have a precedent for adding meta tags to documents already) and drop its body and attachments, since we're intending to keep the existing disk value for its leaf always. In the updater if that revision still exists in the revtree we perform the rev merge and keep the disk (leaf) value as is. Fix: #6162 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
