Uploaded image for project: 'Go Driver'
  1. Go Driver
  2. GODRIVER-3032

Clarify exactly what code/label fields drivers should inspect to determine retryability

XMLWordPrintableJSON

    • Type: Icon: Spec Change Spec Change
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Retryability
    • None
    • Hide

      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
      Show
      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
    • Hide

      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?

      Show
      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?

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

            Assignee:
            Unassigned Unassigned
            Reporter:
            dbeng-pm-bot PM Bot
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: