[SERVER-59740] Add more end-to-end tests for time-series measurement indexes Created: 02/Sep/21  Updated: 27/Oct/23  Resolved: 24/Jan/22

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

Type: Task Priority: Major - P3
Reporter: David Percy Assignee: Backlog - Query Optimization
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-59505 Time-series query on mixed, nested me... Closed
Assigned Teams:
Query Optimization
Sprint: QO 2021-10-04, QO 2021-11-29, QO 2021-12-13, QO 2021-12-27, QO 2022-01-10, QO 2022-01-24, QO 2022-02-07
Participants:

 Description   

Let's make sure we have test coverage for various types of time-series queries that should use secondary indexes on measurements. Some index types didn't require any Query work, but we should confirm that the planner uses the indexes when available, and that the results are correct.



 Comments   
Comment by David Percy [ 02/Sep/21 ]

One example we should look at is sparse indexes.

This seems related to SERVER-59505: it's possible for a bucket's control.min.a.b / control.max.a.b to both be missing, even if a.b is non-missing on some of its events.

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