Currently, when the collection does not exist, `$listSearchIndexes` returns a cursor and, when getMore is called on that cursor, a `NamespaceResolution` exception is thrown.
This does not match how the aggregation pipeline works for other stages. With a `$group` stage, for example, getMore returns an empty cursor in this case, rather than throwing a `NamespaceResolution` exception.
Example with `$listSearchIndexes`:
Aggregate call:
Command: {"aggregate": "slava-test-collection", "pipeline": [{"$listSearchIndexes": {}}], "cursor": {"batchSize": 0}, "$db": "slava-test", "$clusterTime": {"clusterTime": {"$timestamp": {"t": 1689011240, "i": 1}}, "signature": {"hash": {"$binary": {"base64": "UbqmSAzjXtJNn8TiKdCv/NBV/SA=", "subType": "00"}}, "keyId": 7253089058631450627}}, "lsid": {"id": {"$binary": {"base64": "yj+/sud8QdKifNmSLv6fDg==", "subType": "04"}}}}
Command reply: {"cursor": {"firstBatch": [], "id": 5529230180027818871, "ns": "slava-test.slava-test-collection"}, "ok": 1.0
Cursor getMore call:
Command: {"getMore": 5529230180027818871, "collection": "slava-test-collection", "$db": "slava-test",
{"ok": 0.0, "errmsg": "Executor error during getMore :: caused by :: Collection 'slava-test.slava-test-collection' does not exist.", "code": 26, "codeName": "NamespaceNotFound"}}
- causes
-
CSHARP-4755 Disable Atlas Search Index management tests on Sharded clusters
-
- Closed
-
- is depended on by
-
CSHARP-4736 Enable Atlas Search Index management tests on sharded clusters
-
- Blocked
-
- is related to
-
-
- Blocked
-