[SERVER-58062] Support multikey indexes on time-series measurements Created: 24/Jun/21  Updated: 12/Aug/21  Resolved: 12/Aug/21

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

Type: New Feature Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Dan Larkin-York
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-58057 Support ascending and descending inde... Closed
related to SERVER-59305 Reject timeseries measurements with a... Closed
Sprint: Execution Team 2021-08-23
Participants:

 Description   

A multikey index will use the time-series buckets non-positional min and max data to build the index. The same indexes will be created as described in the ascending and descending indexes ticket. This works well for non-positional queries such as db.multi.find({data: 5}) or db.multi.find({data: {$gt: 9}}). For positional queries such as db.multi.find({data: [5]}) or db.multi.find({data: [5, 9]}), the non-positional min and max data can be computed from the query. The indexes can then be used to find the time-series buckets that satisfy the min and max range of the query. Any time-series buckets that match this criterion will need to have their measurements looked over for matches.



 Comments   
Comment by Dan Larkin-York [ 12/Aug/21 ]

Closing out as "won't do" in favor of doing SERVER-59305 instead. Can reconsider in the future.

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