[SERVER-84531] Inserting mixed-schema buckets through the system.buckets collection doesn't set the timeseriesBucketsMayHaveMixedSchemaData flag Created: 03/Jan/24  Updated: 02/Feb/24

Status: In Code Review
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

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

Issue Links:
Backports
Related
is related to SERVER-84699 Add a check to validation to check fo... Open
Assigned Teams:
Storage Execution
Operating System: ALL
Backport Requested:
v7.3
Sprint: Execution Team 2024-02-05, Execution Team 2024-02-19
Participants:

 Description   

All newly created time-series collections have timeseriesBucketsMayHaveMixedSchemaData set to false. This flag never gets changed as time-series inserts through the view can never result in mixed-schema buckets. However, one can still insert mixed-schema buckets through the system.buckets collection (direct write) and we wouldn't update the flag to true. mongodump/mongorestore does this. We should check whether buckets inserted via direct writes contain mixed-schema data and set the flag appropriately.


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