[SERVER-81928] Move noPassthrough queryStats tests into core/ Created: 06/Oct/23  Updated: 27/Oct/23  Resolved: 13/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Charlie Swanson
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Integration
Sprint: QI 2023-10-30
Participants:

 Description   

Many of the tests in https://github.com/mongodb/mongo/tree/7e9ee5d1955a12d162eb96a8709585c689394d57/jstests/noPassthrough/queryStats feel like they could be in core/ and get passthrough coverage.

If they require replication or sharding, we should just denylist them from the appropriate suites with "requires_sharding" or "requires_replication" tags.



 Comments   
Comment by Charlie Swanson [ 13/Oct/23 ]

judah.schvimer@mongodb.com the tests here all need to set a parameter to configure the query stats rate limit to be non-zero (default off). In addition, any passthrough fixture that runs these back to back would need to (a) clear the query stats store between tests and (b) not run any other queries concurrently that would show up.

 

I don’t think we have a great way to do this, and we have the reverse scenario covered: running core and aggregate while enabling query stats. 

with all that context, do you have any further suggestions here? Or should we close this out?

Generated at Thu Feb 08 06:47:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.