[SERVER-37983] createIndexes should validate the 'expireAfterSeconds' option value Created: 07/Nov/18 Updated: 06/Dec/22 Resolved: 08/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 3.6.8, 4.0.4, 4.1.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | James Wahlin | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Duplicate | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: | The following index creation succeeds:
Leading to the following logged error message when TTL expiration runs:
|
||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
The createIndexes command does not validate the type for a 'expireAfterSeconds' option when specified. Instead validation is performed at TTL job run time, resulting in the given index being skipped for consideration. Instead we should fail the createIndexes command when the value provided for 'expireAfterSeconds' is not valid. |
| Comments |
| Comment by James Wahlin [ 08/Nov/18 ] |
|
Closing as a duplicate of |
| Comment by Asya Kamsky [ 08/Nov/18 ] |
|
Dup of |