-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Write Ops
-
None
-
Query Execution
From SERVER-21726, it became clear that we need a new way to detect no-ops from update modifiers that works for all storage engines and regardless of whether replication is active.
- related to
-
SERVER-21726 WiredTiger primaries replicate no-op update, leading to out-of-sync secondaries and data loss
- Closed
-
SERVER-36405 Update should be smarter about recognizing noop updates by comparing original and "updated" documents
- Backlog