[SERVER-74313] Prevent "invalid view definition" error during AutoGetCollection for a non-existing collection Created: 23/Feb/23  Updated: 02/Mar/23

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

Type: Bug Priority: Major - P3
Reporter: Allison Easton Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: views
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-72673 Investigate if it's ok to ignore err... Closed
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 Description   

Currently, AutoGetCollection for an unknown namespace will fail with InvalidView even if there is no view for the namespace we are looking up. In a sharded collection, this means that commands sent to shards that do not know about a collection will fail for this reason.

SERVER-73984 aims to make setAllowMigrations send flushRoutingTableCacheUpdates to all shards (even if they don't have chunks for the collection). With the current AutoGetCollection behavior, this would mean that in a database with an invalid view, all ddl operations in that database would fail with InvalidView even when the ddl operation has nothing to do with the invalid view.

If possible, we should implement something similar to SERVER-42373 to allow AutoGetCollection to succeed if the namespace is not a view.


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