[SERVER-60034] Prohibit sparse indexes on time-series measurements Created: 16/Sep/21  Updated: 29/Oct/23  Resolved: 17/Sep/21

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

Type: Bug Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2021-10-04
Participants:

 Description   

We have run into an issue here, where having multiple types for the same field can cause issues. For example, consider an index on x.y. If one measurement has {x: 5}, one has {x: <date>}, and one has {x: {y: true}}, then the min will be 5, the max will be <date>, and the bucket will not be indexed since x.y is undefined in min and max.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 17/Sep/21 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-60034 Prohibit sparse indexes on time-series measurements
Branch: master
https://github.com/mongodb/mongo/commit/a49f2872e308880f43da2d7ef7502983f6cbe445

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