[SERVER-60385] The CatalogCache shouldn't assume that the timeseries fields are immutable Created: 01/Oct/21  Updated: 29/Oct/23  Resolved: 04/Oct/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.1.0-rc0

Type: Task 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

Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-10-04
Participants:

 Description   

Similar to SERVER-59808 but this time for the CatalogCache.

The change is very straight-forward: we need to extend the ChunkManager::makeUpdated function with the timeseries field.



 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 [ 04/Oct/21 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-60385 Timeseries fields aren't immutable anymore
Branch: master
https://github.com/mongodb/mongo/commit/f4aa2b0e25976facd7bda02872e2a46205975dcc

Generated at Thu Feb 08 05:49:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.