[SERVER-66496] Investigate premature bucket closures in timeseries collections Created: 16/May/22 Updated: 27/Oct/23 Resolved: 04/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pavithra Vetriselvan | Assignee: | Pavithra Vetriselvan |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Sprint: | Execution Team 2022-05-30, Execution Team 2022-06-13, Execution Team 2022-06-27, Execution Team 2022-07-11, Execution Team 2022-08-08 | ||||
| Participants: | |||||
| Linked BF Score: | 18 | ||||
| Comments |
| Comment by Pavithra Vetriselvan [ 04/Aug/22 ] |
|
Yes, I think we can close this ticket as Works As Designed and handle the test failures separately. Maybe we can convert the checks to be a greater than or equal to comparison versus an exact match, but I haven't thought through whether that can be generalized throughout most tests while also being correct. |