[SERVER-78831] Make $listSearchIndexes throw an Exception when used outside of Atlas Created: 10/Jul/23  Updated: 29/Oct/23  Resolved: 20/Jul/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 7.0.2, 6.0.11

Type: Task Priority: Major - P3
Reporter: Evan Plotkin Assignee: Hima Sheth (Inactive)
Resolution: Fixed Votes: 0
Labels: pm3294-m3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-81055 $listSearchIndexes does not throw whe... Closed
related to SERVER-78331 Ensure $vectorSearch is disabled when... Closed
Assigned Teams:
Query Integration
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.0, v6.0
Participants:

 Description   

The search index management commands throw the following exception when used outside of atlas:

 
Command failed with error 115 (CommandNotSupported): 'Search index commands are only supported with Atlas.' on server localhost:27017. The full response is {"ok": 0.0, "errmsg": "Search index commands are only supported with Atlas."
 
The $listSearchIndexes aggregation stage should also throw a similar exception, noting that $listSearchIndexes is only supported with Atlas.



 Comments   
Comment by Githook User [ 05/Sep/23 ]

Author:

{'name': 'Alyssa Wagenmaker', 'email': 'alyssa.wagenmaker@mongodb.com', 'username': 'awagenmaker'}

Message: SERVER-78831 Better error messages for search-related stages when enterprise is not enabled

Co-authored-by: Ted Tuckman <ted.tuckman@mongodb.com>
Co-authored-by: Hima Sheth <hima.sheth@mongodb.com>
Branch: v6.0
https://github.com/mongodb/mongo/commit/0222c55bd13e7f7b16524085b743e1ed99ab5bcc

Comment by Githook User [ 19/Jul/23 ]

Author:

{'name': 'hima sheth', 'email': '55309402+himasheth@users.noreply.github.com', 'username': 'himasheth'}

Message: SERVER-78831 Make $listSearchIndexes throw an Exception when used outside of Atlas
Branch: master
https://github.com/mongodb/mongo/commit/37fd3eeec97eb166267671bffe39ee07fe0a2c44

Comment by Slav Babanin [ 10/Jul/23 ]

It appeared in enterprise version 7.0.0-rc3

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