[SERVER-66692] Allow creating TTL index over timeField with partialFilterExpression defined over metaField Created: 23/May/22  Updated: 29/Oct/23  Resolved: 10/Jun/22

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

Type: Improvement Priority: Major - P3
Reporter: Dan Larkin-York Assignee: Fausto Leyva (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-67144 Prevent downgrade with TTL index on t... Closed
Duplicate
duplicates SERVER-63549 Partial Expression TTL Indexing for T... Closed
Related
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-05-30, Execution Team 2022-06-13, Execution Team 2022-07-11
Participants:
Case:

 Description   

We should reject any TTL index that is created over a field other than the collection timeField, as well as any TTL index that does not include a partialFilterExpression. The partialFilterExpression should only be allowed to access the metaField (constant across measurements within a bucket), and not any measurement data. We should be able to reuse some existing code for checking and re-writing the partialFilterExpression.



 Comments   
Comment by Githook User [ 10/Jun/22 ]

Author:

{'name': 'Faustoleyva54', 'email': 'fausto.leyva@mongodb.com', 'username': 'Faustoleyva54'}

Message: SERVER-66692 Allow creating TTL index over timeField with partialFilterExpression defined over metaField
Branch: master
https://github.com/mongodb/mongo/commit/7ad95de6d0d0ff06f5161f7d5e3243b0cdd5e9cc

Generated at Thu Feb 08 06:06:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.