[SERVER-60565] Ensure newly created time-series buckets do not contain problematic mixed-schema data Created: 08/Oct/21  Updated: 11/Oct/23  Resolved: 27/Oct/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: Dan Larkin-York Assignee: Dan Larkin-York
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-60978 Refactor timeseries::MinMax and re-us... Closed
Problem/Incident
Sprint: Execution Team 2021-10-18, Execution Team 2021-11-01
Participants:
Linked BF Score: 135

 Description   

Currently buckets are allowed to contain measurement with arbitrarily mixed schema. This can lead to complicated type-comparison semantics (as seen in SERVER-59505). In order to facilitate indexing, we need to maintain certain invariants about what types of data can co-exist within a single bucket.

This will require changes to the time-series insert path. Namely, our current MinMax structure for maintaining the control summary data will be retrofitted to determine if an incoming measurement contains an incompatible schema relative to the measurements which have already landed in a given bucket. If so, we will close the bucket and open a new one for the new measurement.



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

Author:

{'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}

Message: SERVER-60565 Ensure newly created time-series buckets do not contain problematic mixed-schema data
Branch: master
https://github.com/mongodb/mongo/commit/dd8c32c66cbb401af315364e8d6843e521d96e72

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