Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: 8.0 Required
Affects Version/s: None
Component/s: None
Labels:
- server-rapid-response

Assigned Teams:

Catalog and Routing
Backport Requested:

v8.0

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.

is depended on by

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

Blocked

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

Blocked

SERVER-90568 movePrimary must clone timeseriesBucketsMayHaveMixedSchemaData catalog option

Blocked

is related to

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-84699 Add a check to validation to check for mixed-schema buckets for time-series

Closed

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

Closed

(2 related to)

Assignee:: Pierlauro Sciarelli

Reporter:: Pierlauro Sciarelli

Participants:: Pierlauro Sciarelli

Votes:: 0 Vote for this issue

Watchers:: 11 Start watching this issue

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

Updated:: Jul 01 2024 07:51:47 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates