-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Execution Team 2021-11-01, Execution Team 2021-11-15
Users that upgrade from earlier versions of the server may contain mixed-schema data in their time-series buckets. As long as the catalog flag that indicates whether a time-series bucket may contain mixed-schema data is set to true, we need to validate all the buckets when trying to index time-series measurements.
There are two possible outcomes:
- There are no buckets containing mixed-schema data. We set the catalog flag to false and subsequent index builds do not have to perform any validation on the buckets.
- There is at least one bucket containing mixed-schema data. The index build will fail in this case. We'll also provide a list of options for migrating the time-series buckets to a format that does not contain problematic mixed-schema data.
- causes
-
SERVER-69264 Fail time-series index builds due to mixed schema only at commit time
- Closed
- is related to
-
SERVER-61070 Update time-series mixed-schema data index failure error message
- Closed