Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Storage Execution
Sprint:
Storage Execution 2025-09-29
CAR Domain/s:
None

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

There are currently two known causes for invalid mixed schema data (~~SERVER-107361~~ and ~~SERVER-91194~~). These can be differentiated by examining bucket size and measurement count, we should do so in validation results to improve clarity in validation failures.

is related to

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

Closed

SERVER-107361 Rollover determination in the bucket catalog can fail to check mixed schema for large measurements

Closed

Assignee:: Binh Vo
Reporter:: Binh Vo
Participants:: Binh Vo, TPM Jira Automations Bot
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Due:: 01/Nov/25
Created:: Sep 16 2025 06:58:33 PM UTC
Updated:: Sep 17 2025 01:53:24 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates