-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Fully Compatible
-
Execution Team 2021-10-18
The problem specifically is that all query operations default to ignoring prepare conflicts. Some queries, however, like $setWindowFields may spill to the storage engine, which requires changing the prepare conflict behavior to kIgnoreConflictsAllowWrites, which allows these writes to succeed.
We can work around this problem by allowing all read-only queries (even those that spill to the storage engine) to use kIgnoreConflictsAllowWrites. Special care should be taken for write operations to continue enforcing prepare conflicts
- is depended on by
-
SERVER-59772 Enable setWindowFields in transactions or with readConcern snapshot
-
- Closed
-
-
SERVER-58436 Implement spilling HashAgg
-
- Closed
-
- related to
-
-
- Closed
-