[SERVER-67597] Handle new time-series bucketing parameters on downgrade Created: 28/Jun/22 Updated: 29/Oct/23 Resolved: 26/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Fausto Leyva (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-10-31 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
On attempted downgrade, we need to check each time-series collection and ensure that 'bucketMaxSpanSeconds' and 'bucketRoundingSeconds' correspond to a valid 'granularity' setting, and refuse to perform the downgrade if not.
Additionally, we need to ensure that 'granularity' is set to the appropriate value, and remove 'bucketRoundingSeconds' from the options in order to proceed with the downgrade. |
| Comments |
| Comment by Githook User [ 26/Oct/22 ] |
|
Author: {'name': 'Faustoleyva54', 'email': 'fausto.leyva@mongodb.com', 'username': 'Faustoleyva54'}Message: |