[SERVER-59808] The ShardServerCatalogCacheLoader shouldn't assume that the timeseries fields are immutable Created: 07/Sep/21 Updated: 29/Oct/23 Resolved: 14/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Sergi Mateo Bellido |
| 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: |
v5.0
|
||||
| Sprint: | Sharding EMEA 2021-09-06, Sharding EMEA 2021-09-20 | ||||
| Participants: | |||||
| Description |
|
In 5.0 the timeseries fields were immutable (i.e. we couldn't change their value over time). That is not true anymore: in 5.1 we have some fields, such as the granularity, whose values may be changed by the user. |
| Comments |
| Comment by Sergi Mateo Bellido [ 14/Oct/21 ] |
|
We only need to backport this ticket if the timeseries information that we keep in the Sharding Catalog is mutable. |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 08/Sep/21 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: |