[SERVER-80442] Remove logic to fix invalid expireAfterSeconds values post-creation Created: 25/Aug/23  Updated: 29/Aug/23

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

Type: Task Priority: Major - P3
Reporter: Dan Larkin-York Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: techdebt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Storage Execution
Participants:

 Description   

We introduced additional validation code for TTL indexes in an earlier release cycle, as well as code to fix invalid expireAfterSeconds values for existing indexes. Additionally, we introduced similar logic to normalize any non-integer expireAfterSeconds values to integer values in SERVER-77828.

After we have gone through a major release cycle, we will know that future versions of the server will never see those invalid index specs on disk, as they would have to have first upgraded through a patched version which would fix the spec.

While we'll always need the validation code during index creation/modification, we can remove some of the extra logic associated with fixing existing indexes.


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