[COMPASS-7503] Investigate changes in SERVER-83003: $listSearchIndexes should throw on non-existent DB Created: 05/Dec/23  Updated: 04/Jan/24  Resolved: 07/Dec/23

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-83003 $listSearchIndexes should throw on no... Closed
Documentation Changes: Not Needed

 Description   
Original Downstream Change Summary

Previously if you ran $listSearchIndexes without Atlas configured without a database the command would not error. Now we raise an error when the database doesn't exist.

Description of Linked Ticket

null



 Comments   
Comment by PM Bot [ 04/Jan/24 ]

Fix Version updated for upstream SERVER-83003:
7.2.1, 7.3.0-rc0

Comment by Basit Chonka [ 07/Dec/23 ]

We always fetch search indexes for an existing namespace within Compass.

Comment by PM Bot [ 05/Dec/23 ]

Fix Version updated for upstream SERVER-83003:
7.3.0-rc0

Generated at Wed Feb 07 22:46:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.