[SERVER-83496] Better handling of the tests that set the system.views collection to inconsistent contents Created: 21/Nov/23  Updated: 30/Nov/23

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

Type: Improvement Priority: Major - P3
Reporter: David Dominguez Sal Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-78615 Poor view drop performance leads to r... Closed
Assigned Teams:
Catalog and Routing
Participants:
Story Points: 2

 Description   

Some tests about the view creation and removal (e.g. invalid_system_views.js) introduce invalid / inconsistent entries in the system.view collection. The expectation is that the database will be responsive, even if the catalog contains invalid entries.

Currently, the view DDL operations are pushed with invalid parameters and assume that the lock acquisition will not validate the parameter in apply_ops.cpp. It would be nice to detect the invalid parameters as early as possible and return an error. For testing purposes, a non verified mode of operation can be used to force the state of system views (or other collections) in the catalog. 


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