Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Critical - P2
Fix Version/s: 8.1.0-rc0, 7.3.4, 7.0.13, 6.0.17, 8.0.0-rc14
Affects Version/s: None
Component/s: None
Labels:
- server-rapid-response

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Backport Requested:

v8.0, v7.3, v7.0, v6.0
Sprint:
CAR Team 2024-07-08, CAR Team 2024-07-22
Case:
Linked BF Score:
200

At the time of writing this ticket, there are 2 collection options in the durable catalog that share the following characteristics:

Are only set on time-series
Are serialized as top-level fields (not part of the options sub-object)
Are defaulted to false at bucket collection creation time

As explained in ~~SERVER-91193~~ and ~~SERVER-91194~~, this may lead to query incorrectness.

Purpose of this ticket is to design a solution for nodes affected by those bugs to self-fix the catalog and to make sure it will not be possible to miss cloning such options in the future.

causes

SERVER-92426 Adapt tests to rely on new timeseriesBucketsMayHaveMixedSchemaData catalog option format

Closed

SERVER-93213 Optimize getTimeseriesBucketsMayHaveMixedSchemaData to parse the storage engine option only once

Closed

depends on

SERVER-92186 Implement simple API to get/set app_metadata from/to wiredtiger config strings

Closed

has to be done before

SERVER-92265 Provide a reliable way to persist additional catalog options rather than using the configString workaround

Backlog

is depended on by

SERVER-91194 timeseriesBucketsMayHaveMixedSchemaData not properly cloned upon data migration/initial sync/restore

Closed

SERVER-90243 ShardCollection/Chunk Migrations/Resharding do not clone some collection catalog options.

Closed

SERVER-90568 movePrimary must clone timeseriesBucketsMayHaveMixedSchemaData catalog option

Closed

is related to

SERVER-92186 Implement simple API to get/set app_metadata from/to wiredtiger config strings

Closed

SERVER-93350 Refactor BSONCollectionCatalogEntry::MetaData to encapsulate the logic for correctly loading the timeseries flag.

Backlog

SERVER-91969 Test initial sync with mixed-schema time-series buckets

Closed

related to

SERVER-91193 timeseriesBucketingParametersHaveChanged not properly cloned upon data migration/initial sync/restore

Closed

SERVER-93014 Setting locally timeseriesBucketsMayHaveMixedSchemaData during MultiIndexBlock::commit might generate catalog inconsistencies

Closed

SERVER-93015 Replace _metadata->timeseriesBucketsMayHaveMixedSchemaData checks with getTimeseriesBucketsMayHaveMixedSchemaData()

Closed

SERVER-84699 Add a check to validation to check for mixed-schema buckets for time-series

Closed

SERVER-93099 Allow collMod with timeseriesBucketsMayHaveMixedSchemaData=false

Closed

SERVER-91624 Detect mixed schema buckets in time series collection validation

Closed

(2 is depended on by, 3 is related to, 6 related to)

Assignee:: Pierlauro Sciarelli

Reporter:: Pierlauro Sciarelli

Participants:: Githook User, Pierlauro Sciarelli

Votes:: 0 Vote for this issue

Watchers:: 15 Start watching this issue

Created:: Jun 05 2024 12:44:30 PM UTC

Updated:: Nov 15 2024 05:31:43 PM UTC

Resolved:: Jul 12 2024 03:01:49 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates