-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Internal Code, Write Ops
-
None
During replication, some updated constraints should be relaxed. For instance, we apply an update even if that path is not "viable" (ie. it changes the data type of a field other than the target field). We'd like to turn on that behavior for replication only, particularly as part of initial sync.
- related to
-
SERVER-6833 Secondary crashes when replicating a document that the primary accepted (with a field name containing a "$")
- Closed