[SERVER-50272] Make RoutingTableHistory movable Created: 12/Aug/20  Updated: 29/Oct/23  Resolved: 20/Aug/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Improvement Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: PM-1645-Milestone-2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-46199 Implement collection cache on top of ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-08-24
Participants:

 Description   

As part of the changes on SERVER-46199 the new CollectionCache will require that the cached elements (of RoutingTableHistory type) to be movable. To allow this there are three neccessary changes:

  • Remove the _sequenceNumber on RoutingTableHistory, that way the RoutingTableHistory merge can be implemented as an inmutable operation, which is necessary for the new lookup pattern to be used for the collection cache
  • Remove the const on the RoutingTableHistory class members
  • Add a move constructor and a move assign operator


 Comments   
Comment by Githook User [ 20/Aug/20 ]

Author:

{'name': 'Marcos José Grillo Ramírez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-50272 Make RoutingTableHistory movable
Branch: master
https://github.com/mongodb/mongo/commit/bc3233c1ff791a91cb85cff6439969f394068d31

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