[SERVER-79499] "Fix" non-time-series bucket collections in tests. Created: 31/Jul/23  Updated: 07/Feb/24

Status: In Code Review
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Felipe Gasper Assignee: Haley Connelly
Resolution: Unresolved Votes: 0
Labels: oldstorexemea, time-series, time-series-mongosync
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-79630 Disallow creating and preventing upgr... Open
Related
related to SERVER-79630 Disallow creating and preventing upgr... Open
Assigned Teams:
Storage Execution
Backport Requested:
v7.0, v6.0
Sprint: Execution EMEA Team 2023-10-16, Execution Team 2024-02-19
Participants:

 Description   

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.



 Comments   
Comment by Felipe Gasper [ 31/Jul/23 ]

Hopefully-complete list of tests in question:

  • jstests/core/clustered/clustered_collection_creation.js
  • jstests/core/timeseries/clustered_index_crud.js
  • jstests/core/timeseries/clustered_index_options.js
  • jstests/core/txns/txn_ops_allowed_on_buckets_coll.js
  • jstests/replsets/rollback_clustered_indexes.js
Generated at Thu Feb 08 06:41:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.