-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
Fully Compatible
-
ALL
-
-
Cluster Scalability 2024-12-23, Cluster Scalability 2025-01-20, Cluster Scalability 2025-02-03
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.
- is depended on by
-
SERVER-99035 Combine AbortResult and CommitResult struct in TXN API
-
- Backlog
-
-
SERVER-99915 FLE2 findAndModify should also return WCE from transaction API result
-
- In Progress
-
-
SERVER-100669 Remove version checks in transactions_wait_for_write_concern.js and speculative_read_transaction.js when v9.0 becomes last-lts
-
- Backlog
-
- is related to
-
SERVER-99035 Combine AbortResult and CommitResult struct in TXN API
-
- Backlog
-
-
SERVER-98338 Improve transaction API interaction with write concern
-
- Backlog
-
- related to
-
SERVER-27067 Some Commands do not wait for write concern for no-op writes
-
- Closed
-
-
SERVER-78311 mongos does not report writeConcernError in presence of writeErrors for insert command
-
- Closed
-
-
SERVER-100943 abortTransaction must wait for write concern and return WCEs on failure
-
- Open
-
- split from
-
SERVER-81246 FLE WriteConcernError behavior unclear
-
- Closed
-