-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2018-02-12
Once featureCompatibilityVersion 3.4-specific behavior is removed, the allowUnsafeRenamesDuringInitialSync flag will no longer be necessary because all collections will have UUIDs and so renames during initial sync will no longer be unsafe. As part of SERVER-32741, the initial_sync_rename_collection_unsafe.js test will be removed. The allowUnsafeRenamesDuringInitialSync flag should be removed as well.
- related to
-
SERVER-32466 Determine and remove featureCompatibilityVersion-dependent Replication code behavior that is only relevant to the 3.4-3.6 transition
- Closed