[SERVER-85919] Adapt convertToCapped and cloneToCapped command to work with tracked unsharded collection Created: 30/Jan/24  Updated: 31/Jan/24  Resolved: 31/Jan/24

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

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Backlog - Catalog and Routing
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-85917 covertToCapped and cloneToCapped comm... Closed
Duplicate
duplicates SERVER-84482 convertToCapped and cloneCollectionAs... Blocked
Assigned Teams:
Catalog and Routing
Participants:

 Description   

Currently these commands do not properly update the sharding catalog and do not take into account that the collection could actually leave in a shard different from the DB primary.


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