[SERVER-67595] Introduce bucketRoundingSeconds time-series option Created: 28/Jun/22 Updated: 29/Oct/23 Resolved: 25/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | David Wang (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Execution Team 2022-07-11, Execution Team 2022-07-25, Execution Team 2022-08-08 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Currently, we have an implicit bucketing parameter that controls how we round down the min timestamp for bucket at creation time. This value is derived from the collection's 'granularity' value. The 'granularity' also controls the 'bucketMaxSpanSeconds' value, which we store explicitly in the collection's time-series options. We want to make the rounding parameter explicit as well, and store it as an optional parameter 'bucketRoundingSeconds'. For this ticket, we will only store the value for newly-created collections. It will still be derived from 'granularity' and cannot be controlled independently. We will defer downgrade work to future tickets. |
| Comments |
| Comment by Githook User [ 25/Jul/22 ] |
|
Author: {'name': 'David Wang', 'email': 'david.wang@mongodb.com', 'username': 'DavidJRWang'}Message: |