-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 7.0.0, 5.0.19, 6.0.8
-
Component/s: None
-
Storage Execution
-
Fully Compatible
-
ALL
-
v7.2, v7.0, v6.0, v5.0
-
Execution Team 2023-11-13, Execution Team 2023-11-27
-
(copied to CRM)
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Our issues with extended-range dates was first surfaced via SERVER-66469, and addressed by a series of follow-up tickets. The end state is correct, but slow query behavior when these dates are present. However, we did not properly address the impact of extended-range dates on TTL behavior, which still uses the bucket _id (OID) for sorting and filtering.
Until we introduce a new bucket _id format that can represent the full date range in properly sorted order, we should disable TTL deletion for time series collections with extended range dates.
- is depended on by
-
-
- Closed
-
- is related to
-
SERVER-97368 Enable TTL deletes on time-series collections containing data prior to 1970
-
- Closed
-
- related to
-
SERVER-88776 return information on time-series collections with TTL feature disabled
-
- Closed
-