[SERVER-47526] Rename collection: Convert usage of getCollectionDescription_DEPRECATED to getCollectionDescription Created: 14/Apr/20  Updated: 29/Oct/23  Resolved: 24/Apr/20

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

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

Issue Links:
Depends
is depended on by SERVER-47521 Remove getCollectionDescription_DEPRE... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-04-20, Sharding 2020-05-04
Participants:

 Description   

As part of PM-1645 we need to make sure that all usages of getCollectionDescription handles StaleShardVersion errors correctly. To make progress easy to follow, we renamed the old implementation getCollectionDescription_DEPRECATED and we're progressively changing it to the new implementation that throws if no collection metadata has been loaded.

In the case of rename collection, besides changing to the new implementation we have to ensure that:

  • The calls to isSharded are performed only on the primary if we're applying a log operation
  • The Collection Sharding State of temporary collections is not being check, considering temporary from the application's perspective
  • All the calls to the rename collection command are passing through a router if the server has been started with the --shardsvr parameter and was added to a cluster


 Comments   
Comment by Githook User [ 24/Apr/20 ]

Author:

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

Message: SERVER-47526 Use getCollectionDescription on rename collection

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