Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-84081

FLE2 write error hides write concern error

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Cluster Scalability
    • ALL
    • Hide

      1. spin up a single-node replica set
      2. create a FLE2 encrypted collection: "basic" using an encrypted client.
      3. run the command: {insert: "basic", documents: [{_id: 1}]}
      4. then, run the command:
      {insert: "basic", documents: [{_id: 1}], writeConcern: {w: 3}}
      5. check that the result of the second insert only contains a DuplicateKey write error, and no UnsatisfiableWriteConcern error

      Show
      1. spin up a single-node replica set 2. create a FLE2 encrypted collection: "basic" using an encrypted client. 3. run the command: {insert: "basic", documents: [{_id: 1}]} 4. then, run the command: {insert: "basic", documents: [{_id: 1}], writeConcern: {w: 3}} 5. check that the result of the second insert only contains a DuplicateKey write error, and no UnsatisfiableWriteConcern error

      If a FLE2 write encounters both a write error and a write concern error (WCE), the WCE is omitted from the response. This is inconsistent with the behavior of writes on normal collections where both the WCE and write errors are included in the response. This issue applies to both mongod and mongos.

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            erwin.pe@mongodb.com Erwin Pe
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: