[SERVER-72705] Introduce upper bound for bucketMaxSpanSeconds and bucketRoundingSeconds Created: 10/Jan/23 Updated: 10/Jan/23 Resolved: 10/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Dan Larkin-York |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Execution Team 2023-01-23 | ||||||||
| Participants: | |||||||||
| Description |
|
We should set some large upper limit for these bucketing parameters to prevent users from accidentally configuring extreme values. A good initial bound might be 30 days, since that's currently the maximum value for span supported with "hours" granularity. |