[SERVER-73879] Improve error messages for out-of-bounds expireAfterSeconds values Created: 10/Feb/23 Updated: 29/Oct/23 Resolved: 02/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Binh Vo |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution NAMER
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution NAMR Team 2023-10-02, Execution NAMR Team 2023-10-16 | ||||||||
| Participants: | |||||||||
| Description |
|
Our current error messages for invalid expireAfterSeconds (TTL) values are pretty vague. It can be difficult for users to understand which values are actually allowed, and this is complicated by the fact that different ranges are allowed between time series collections and secondary indexes. Additionally, we should notify the docs team downstream so that they can update the official docs. |
| Comments |
| Comment by Githook User [ 02/Oct/23 ] |
|
Author: {'name': 'Binh Vo', 'email': 'binh.vo@mongodb.com', 'username': 'binhvomongodb'}Message: |