[GODRIVER-3032] Clarify exactly what code/label fields drivers should inspect to determine retryability Created: 31/Oct/23  Updated: 25/Jan/24

Status: Scheduled
Project: Go Driver
Component/s: Retryability
Affects Version/s: None
Fix Version/s: None

Type: Spec Change Priority: Major - P3
Reporter: PM Bot Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
Related
related to GODRIVER-3085 Require 4.3.1+ server version when us... Backlog
Quarter: FY24Q4, FY25Q1
Upstream Changes Summary:

DRIVERS-1641:
Summary of necessary driver changes

  • Do not use writeConcernError.code in pre-4.4 mongos response to determine retryability.
  • Do not use writeErrors[].code in pre-4.4 server responses to determine retryability.

Commits for syncing spec/prose tests

  • Sync unified retryable writes spec tests with 3e60a7c
Documentation Changes Summary:

1. What would you like to communicate to the user about this feature?
2. Would you like the user to see examples of the syntax and/or executable code and its output?
3. Which versions of the driver/connector does this apply to?


 Description   

This ticket was split from DRIVERS-1641, please see that ticket for a detailed description.


Generated at Thu Feb 08 08:39:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.