-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In search_index_process_router.cpp, fetchCollectionUUIDAndResolveView and resolveViewHelper only check the transport status of the listCollections and _shardsvrResolveView replies, not the command status. As a result, a failed listCollections surfaces as a "wrong type for field" error instead of the shard's error, and a failed _shardsvrResolveView makes a view look like a missing collection (NamespaceNotFound).
We should check both replies with AsyncRequestsSender::Response::getEffectiveStatus and add a sharded test that uses failCommand on each command to verify that search index commands return the shard's error.