-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
CAR Team 2026-03-30, CAR Team 2026-04-13
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Investigate and define the expected behavior of the applyOps command when it replays operations that create timeseries collections and associated system.buckets collections, especially in the presence of potential namespace conflicts.
In particular, this ticket should:
- Clarify whether applyOps should enforce the same timeseries namespace consistency checks (e.g. conflicting regular collection vs system.buckets timeseries collection) that we run for normal user commands, or whether it should more closely mimic secondary oplog application and allow recreating historically inconsistent states.
- Decide if we need an explicit mechanism such as an isForApplyOps flag, or similar, in the create-collection/timeseries path to distinguish applyOps creates from ordinary user commands.
- is related to
-
SERVER-121290 Always use new timeseries create path
-
- In Code Review
-