[SERVER-59741] Enable more timeseries tests on sharded-collections passthrough Created: 02/Sep/21  Updated: 29/Oct/23  Resolved: 01/Nov/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.2.0

Type: Task Priority: Major - P3
Reporter: David Percy Assignee: David Percy
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-57567 Update sharded passthrough suite to h... Closed
is related to SERVER-55516 Remove tags for Time-series tests in ... Closed
Backwards Compatibility: Fully Compatible
Sprint: QO 2021-09-20, QO 2021-10-04, QO 2021-10-18, QO 2021-11-01, QO 2021-11-15
Participants:

 Description   

Now that createCollection(..., {timeseries: ...}}) generally works with the sharded-collections passthrough suite, we should make sure we enable as many individual tests as possible.

In particular, some are disabled because "The shardCollection implicitly creates an index on time field.".  That seems like something we can enable.



 Comments   
Comment by Githook User [ 28/Oct/21 ]

Author:

{'name': 'David Percy', 'email': 'david.percy@mongodb.com', 'username': 'dpercy'}

Message: SERVER-59741 Enable more sharded-collections time-series tests
Branch: master
https://github.com/mongodb/mongo/commit/c3f615c8112e54873b55677b8df2af84eaa521c7

Comment by David Percy [ 13/Oct/21 ]

Also check for tests that use getSiblingDB().  I think the passthrough suite only implicitly shards the default db, so a test that uses getSiblingDB() may not actually be testing the sharded-collections behavior, even if it runs in the sharded-collections passthrough suite.  Never mind, that's not true at all.  It looks like the sibling DBs are implicitly sharded too.

Generated at Thu Feb 08 05:48:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.