[SERVER-30798] Disallow running applyOps with a renameCollection entry that renames across databases Created: 23/Aug/17  Updated: 06/Dec/22

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-30371 Separate renameCollection across DB c... Closed
Related
related to SERVER-32952 applyOps does not validate updates Backlog
Assigned Teams:
Replication
Participants:

 Description   

Starting in 3.6 we no longer replicated renameCollection across databases as its own oplog entry. Instead we log each component operation of the rename individually. 3.6 still needs to support applying those oplog entries to support someone who backs up a 3.4 replica set and wants to restore it to 3.6. But in 3.8+ we don't need to support interoperability with 3.4, so we should remove support for applying these types of oplog entries


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