-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Storage Execution
-
Fully Compatible
-
v7.3, v7.0, v6.0
-
Execution EMEA Team 2023-10-16, Execution Team 2024-02-19, Execution Team 2024-04-01, Execution Team 2024-04-15
-
9
Some of the server's tests create `system.buckets.*` collections that aren't time-series buckets.
The server's public documentation says that "system." collections are for internal use and should not be created directly. It also says specifically that system.buckets collections are for time-series use. Thus, the server's tests that do this are testing functionality that we don’t expect from users.
Mongosync uses the server's tests to test its own functionality. We could skip the tests that create non-time-series buckets, but that's unideal because it means less test coverage for mongosync.
This ticket proposes modification of these server tests either to:
- use a non-system.buckets name for non-time-series collections
- create those collections as time-series
... so that the server's tests model its expected inputs.
- is depended on by
-
SERVER-79630 Disallow creating and preventing upgrading with system.buckets namespaces which aren't timeseries collections
-
- Open
-
- related to
-
SERVER-87231 Catalog drop collection command should not translate timeseries namespaces if no timeseries options are present
-
- Closed
-
-
-
- Needs Scheduling
-
-
-
- Open
-