Closed martinsumner closed 1 year ago
@yorkshire-steve - this has been resolved a different way to our discussion, as I considered that simply over-riding node_confirms in the request options for the specific fetch case to be a bit a fragile. Now the response failure for node_confirms is only generated when there has been no "Expected Clock" match
When fetching an object for replication, enough nodes are found if the expected clock is true - but that might then fail on node_confirms. Don't generate the node_confirms response error if there has been a match on the expected clock.