[SERVER-33064] Remove allowUnsafeRenamesDuringInitialSync flag Created: 01/Feb/18  Updated: 29/Oct/23  Resolved: 09/Feb/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.7.2

Type: Task Priority: Major - P3
Reporter: Maria van Keulen Assignee: William Schultz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-32466 Determine and remove featureCompatibi... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-02-12
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 09/Feb/18 ]

Author:

{'email': 'william.schultz@mongodb.com', 'name': 'William Schultz', 'username': 'will62794'}

Message: SERVER-33064 Remove 'allowUnsafeRenamesDuringInitialSync' flag
Branch: master
https://github.com/mongodb/mongo/commit/1e9f9c65a8fa0cd642c7cc7df43949f00bc971fe

Generated at Thu Feb 08 04:32:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.