The _durableTimeseriesBucketsMayHaveMixedSchemaData and _durableTimeseriesBucketingParametersHaveChanged flags introduced by SERVER-98399 and SERVER-91231 respectively, do not respect point-in-time catalog lookups, and are instead always read "at latest".
This is because they are placed inside CollectionImpl::SharedState which is shared by the various versions of the collections.
In order to properly support point-in-time reads (e.g. for readConcern: snapshot or background validate) they should be moved to a data structure that is versioned according to the read timestamp.
- is depended on by
-
SERVER-104757 Remove unnecessary fsync from timeseries mixed schema bucket tests
-
- Closed
-
- is related to
-
SERVER-91231 Get rid of md.timeseriesBucketingParametersHaveChanged for avoiding confusion/misuses
-
- Closed
-