[SERVER-75918] Handle missing time-series options fields in the sharding catalog for existing collections Created: 10/Apr/23 Updated: 29/Oct/23 Resolved: 21/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0, 7.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Yuhong Zhang | Assignee: | Yuhong Zhang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v7.0
|
||||||||||||||||
| Sprint: | Execution Team 2023-04-17, Execution Team 2023-05-01 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
For existing sharded time-series collections, it is possible to have unset fields like granularity or bucketMaxSpanSeconds in the sharding catalog. Some callers that read these fields expect valid values, so we should either generate them on the fly while reading them, or fix them in the sharding catalog lazily. |
| Comments |
| Comment by Githook User [ 21/Apr/23 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'yuhong.zhang@mongodb.com', 'username': 'YuhongZhang98'}Message: (cherry picked from commit 252d3c0001afe2cd5027d1354a6ad012de87ba6b) |
| Comment by Githook User [ 21/Apr/23 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'yuhong.zhang@mongodb.com', 'username': 'YuhongZhang98'}Message: |