[SERVER-71667] The drop of a sharded collection should not trigger the check for the existence of invalid views Created: 29/Nov/22  Updated: 29/Oct/23  Resolved: 01/Dec/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 6.0.3, 6.1.0-rc4, 6.2.0-rc2
Fix Version/s: 6.3.0-rc0

Type: Task Priority: Major - P3
Reporter: Paolo Polato Assignee: Paolo Polato
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Problem/Incident
is caused by SERVER-71085 DropCollectionCoordinator should only... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.2, v6.1, v6.0
Sprint: Sharding EMEA 2022-12-12
Participants:
Linked BF Score: 153

 Description   

SERVER-71085 introduced new logic in release 6.3 that may cause CollectionCatalog::lookupView() to be invoked within the context of a collName.drop() execution (and consecutively, to raise an InvalidViewDefinition exception in case corrupted data are detected).

This behaviour goes against what was implemented in SERVER-42373 - and this is why SERVER-71085 also introduced a try/catch clause to not propagate such error (and make the needed deductions when it is detected).

For collName.drop() to maintain the semantics established by SERVER-42373 in multiversion cluster, the try/catch clause needs to also be backported to previous release branches.



 Comments   
Comment by Githook User [ 01/Dec/22 ]

Author:

{'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}

Message: SERVER-71667 Add invalid_system_views_sharded_collection.js to the list of required backports for multiversion suites
Branch: master
https://github.com/mongodb/mongo/commit/4e8e3c318e0d4d3c531d197d84f4560218dcf726

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