nickva commented on issue #5422: URL: https://github.com/apache/couchdb/issues/5422#issuecomment-2655559239
Thank you for your patience and sorry for the delay in responding > Is there any way to avoid an attachment getting sent over again during replication even though it already exists in both databases? I think you're absolutely correct, we should be able to avoid resending already existing attachments. We even have a mechanism for it: `_revs_diff` on the target returns a `possible_ancestors` revision list. Then we pass that list in `atts_since` parameter to `_bulk_get` and/or plain GET with `open_revs=[RevsList...]&atts_since=[AttsSinceRevList...]` But, somehow it doesn't work or stopped working at some point. The last major change in that area was the _bulk_get usage and the heuristic to skip calling `_revs_diff` if the target seems to be empty, so I suspect it's something I did that messed it up and I probably errored on the side of caution and opted to always fetch the attachments. Let's keep the issue open, we should investigate this a bit more. -- 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]
