-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
v8.0
-
CAR Team 2024-02-19, CAR Team 2024-03-04, CAR Team 2024-03-18, CAR Team 2024-04-01, CAR Team 2024-04-15, CAR Team 2024-04-29
-
168
SERVER-81190 only tracked "simple" collections. As a follow-up ticket, we can now start supporting the tracking of timeseries collection coming from the
command.
Note that this ticket does not duplicate SERVER-81495 which enabled (and tested) timeseries only from the createUnsplittableCollection test command.
- depends on
-
SERVER-81190 Support tracking "simple" unsharded collections in the sharding catalog
- Closed
- is depended on by
-
SERVER-85838 shardCollection with Time Series options on an existing normal collection must fail
- Backlog
-
SERVER-87797 Adapt timeseries_multiple_mongos.js to unsplittable timeseries collection
- Closed
-
SERVER-89349 Resharding a timeseries during insertion does not leave the bucket collection optimally compressed
- Closed
-
SERVER-89764 Re-enable timeseries tests excluded from balancer suites due to bucket document counting
- Closed
- related to
-
SERVER-89708 Investigate why jstests/concurrency/fsm_workloads/timeseries_mixed_operations.js fails in case of concurrent moveCollection
- Closed
-
SERVER-89825 Investigate why jstests/concurrency/fsm_workloads/timeseries_mirrored_writes.js fails in case of concurrent moveCollection
- Closed
-
SERVER-87233 Skipping if local non-timeseries collection exists check when creating a sharded timeseries collection
- Needs Scheduling