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.
- is depended on by
-
TOOLS-3495 Investigate changes in SERVER-84531: Inserting mixed-schema buckets through the system.buckets collection doesn't set the timeseriesBucketsMayHaveMixedSchemaData flag
- Closed
- is related to
-
SERVER-92222 CannotInsertTimeseriesBucketsWithMixedSchema error code is mismatched between v7.3 and v8.0+
- Closed
-
SERVER-84699 Add a check to validation to check for mixed-schema buckets for time-series
- Closed
-
SERVER-87975 Backportable fix for inserting mixed-schema buckets through the system.buckets collection doesn't set the timeseriesBucketsMayHaveMixedSchemaData flag
- Closed
-
SERVER-91969 Test initial sync with mixed-schema time-series buckets
- Closed