[SERVER-80982] Rename collection coordinator should use the view catalog to check if a view exists Created: 12/Sep/23  Updated: 29/Oct/23  Resolved: 19/Sep/23

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

Type: Bug Priority: Major - P3
Reporter: Enrico Golfieri Assignee: Enrico Golfieri
Resolution: Fixed Votes: 0
Labels: shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2023-09-18, Sharding EMEA 2023-10-02
Participants:
Linked BF Score: 26
Story Points: 1

 Description   

After BACKPORT-16595 the rename collection coordinator checks the source input namespace is not a view. However, it uses the collection catalog instead of the view catalog, which before v6.0 were separated. This is causing rename_collection_view.js to fail due to a wrong error



 Comments   
Comment by Githook User [ 18/Sep/23 ]

Author:

{'name': 'egol', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}

Message: SERVER-80982 Rename collection coordinator should use the view catalog to check if a view exists
Branch: v5.0
https://github.com/mongodb/mongo/commit/84d8a7bdadfa5a9de3a296da378d1324f6b7be82

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