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.