Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0, 7.3.4, 7.0.13, 6.0.17, 8.0.0-rc11
Affects Version/s: None
Component/s: None
Labels:
- storex-ranked
- storex-shortlist

Assigned Teams:

Storage Execution
Backwards Compatibility:
Fully Compatible
Backport Requested:

v8.0, v7.3, v7.0, v6.0
Sprint:
Execution Team 2024-06-24, Execution Team 2024-07-08
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Due to ~~SERVER-84531~~, we need a way to scan a time-series collection to check whether there are buckets with mixed-schema data present. If there are, we'll need to flip the timeseriesBucketsMayHaveMixedSchemaData catalog entry flag to true.

causes

SERVER-92045 Mixed-schema time-series bucket validation check does not set valid flag on error

Closed

is duplicated by

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

Closed

is related to

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

Closed

SERVER-91195 Provide a generic backportable solution not to miss top-level timeseries collection options

Closed

related to

SERVER-84531 Inserting mixed-schema buckets through the system.buckets collection doesn't set the timeseriesBucketsMayHaveMixedSchemaData flag

Closed

Assignee:: Cannon Caspar (Inactive)
Reporter:: Gregory Wlodarek
Participants:: Cannon Caspar, Githook User, Gregory Wlodarek
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Jan 09 2024 06:57:54 PM UTC
Updated:: Aug 07 2024 06:42:07 PM UTC
Resolved:: Jun 28 2024 08:53:19 PM UTC
Confidence Status Last Update:: 12/Jun/24 5:16 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates