[DOCS-16413] Investigate changes in SERVER-81055: $listSearchIndexes does not throw when used outside of atlas in 7.2 alpha releases Created: 02/Oct/23  Updated: 05/Feb/24  Resolved: 15/Nov/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 7.2.0-rc0, 7.0.3, 7.1.1

Type: Task Priority: Critical - P2
Reporter: Backlog - Core Eng Program Management Team Assignee: Kenneth Dyer
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-81055 $listSearchIndexes does not throw whe... Closed
Participants:
Days since reply: 2 days ago

 Description   
Original Downstream Change Summary

Queries that used to succeed with no results if not configured correctly will now fail with an error message

Description of Linked Ticket

https://jira.mongodb.org/browse/SERVER-78831 recently fixed a bug with the $listSearchIndexes aggregation pipeline stage to cause it to throw an error when not connected to an Atlas cluster. Example output from 7.0.1:

>  db.adminCommand({ buildInfo: 1 }).version
7.0.1
> db.bar.getSearchIndexes()
MongoServerError: PlanExecutor error during aggregation :: caused by :: Search index commands are only supported with Atlas.

There appears to be a regression in the 7.2 alpha releases. This fix is no longer present and $listSearchIndexes returns an empty array when executed against a non-Atlas cluster. Example from 7.2.0-alpha-39-g3e9f147:

>  db.adminCommand({buildInfo: 1}).version
7.2.0-alpha-39-g3e9f147
>  db.bar.getSearchIndexes()
[]

 

 



 Comments   
Comment by Education Bot [ 05/Feb/24 ]

Fix Version updated for upstream SERVER-81055:
7.1.1, 7.2.0-rc0, 7.0.3

Generated at Thu Feb 08 08:15:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.