Mandate raising writeConcernError (change SHOULD to MUST)

ExportXMLWordPrintableJSON

    • Hide

      DRIVERS-3684:
      Summary of necessary driver changes

      • Sync new unified tests

      Commits for syncing spec/prose tests
      (and/or refer to an existing language POC if needed)

      Context for other referenced/linked tickets

      •  
      Show
      DRIVERS-3684 : Summary of necessary driver changes Sync new unified tests Commits for syncing spec/prose tests (and/or refer to an existing language POC if needed) https://github.com/mongodb/specifications/commit/775c4bce1bfe1c409b947eae1f3eab6975fccfe3 https://github.com/mongodb/specifications/commit/eb2ee1e529cf1c2fbf8bd54c32dc32c644306d0d includes a non-blocking follow-up to include errmsg in failpoint errors to match server behavior. Context for other referenced/linked tickets  
    • None
    • Hide

      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.

      Show
      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.
    • None
    • None
    • None
    • None
    • None
    • None

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

      Expected Behavior

      As a... (who is this affects)
      I expect... (describe behavior)
      When... (trigger action)

      Actual Behavior and Impact

      • What is the actual behavior?
      • If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

      Dependencies

      • upstream and/or downstream requirements and timelines to bear in mind

      Risks/Unknowns

      • What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
      • Is there an opportunity for better cross-driver alignment or testing in this area?
      • Is there an opportunity to improve existing documentation on this subject?

      Acceptance Criteria

      Implementation Requirements

      • functional reqs, potential snafus to avoid, performance targets, etc

      Testing Requirements

      • unit test, spec test sync, etc

      Documentation Requirements

      • DOCSP ticket, API docs, etc

      Follow Up Requirements

      • additional tickets to file, required releases, etc
      • if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward

       

       

       

        1. image-2026-10-27-18-15-38-574.png
          437 kB
          Johnathan Martell

            Assignee:
            Unassigned
            Reporter:
            TPM Jira Automations Bot
            None
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: