[SERVER-81975] Allow sharded target collection on internalRenameIfOptionsAndIndexesMatch Created: 09/Oct/23  Updated: 26/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-79661 Make "internalRenameIfOptionsAndIndex... Closed
Assigned Teams:
Catalog and Routing
Participants:

 Description   

Remove this condition to disallow renaming to a sharded target collection on 'internalRenameIfOptionsAndIndexesMatch'. This can be done we have defined semantics for $out to a sharded collections (in terms of how the placement, zones, and other sharding details are preserved).


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