[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: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Execution Team 2022-05-30, Execution Team 2022-06-13, Execution Team 2022-07-11 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||
| 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: |