[SERVER-74252] Tests can assume that movePrimary doesn't copy indexes of sharded collections anymore Created: 22/Feb/23  Updated: 29/Oct/23  Resolved: 10/Jul/23

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

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Pol Pinol
Resolution: Fixed Votes: 0
Labels: 7.0UpDown
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-73751 movePrimary shouldn't create indexes ... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Minor Change
Sprint: Sharding EMEA 2023-07-10
Participants:

 Description   

Once 7.0 becomes last LTS, we can assume that the movePrimary operation won't copy indexes of sharded collections.



 Comments   
Comment by Githook User [ 07/Jul/23 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-74252 Update tests to assume that movePrimary doesn't copy indexes of sharded collections
Branch: master
https://github.com/mongodb/mongo/commit/6d4b57f77b1a07a08e82589b1ca88e90800c2c31

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