[SERVER-55187] Support secondary TTL indexes on time-series collections Created: 15/Mar/21  Updated: 06/Dec/22  Resolved: 03/Aug/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Louis Williams Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Participants:

 Description   

Ensure that secondary TTL indexes work on time-series collections.



 Comments   
Comment by Dan Larkin-York [ 03/Aug/21 ]

We discussed this further during the design phase for PM-2189, and decided to cut it from scope. Having a secondary TTL index on the measurements probably doesn't make a lot of sense. Removing individual measurements as they expire would be costly, so we would expire a bucket when all measurements in the bucket expired. It likely isn't a make-or-break feature for customers to be able to do this type of coarse-grained expiry based on a secondary timestamp field (not the primary timestamp field used in the time-series collection definition).

Generated at Thu Feb 08 05:35:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.