-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Indexes
-
None
-
None
-
Developer Tools
Currently when we fetch if search indexes are supported `getIsSearchSupported`
https://github.com/mongodb-js/compass/blob/d5ea17359ef3b6595b81ed27691d6b9fe37f43c2/packages/collection-model/lib/model.js#L333
we set it once and then it's not able to be updated if the cluster then has support. This could lead to confusion if that network request failed, or if search indexes was set up or configured after connecting.
This ticket involves two changes:
- Update the indexes page so that the indexes `Refresh` button will force a re-fetch of the instance model's and collection model's isSearchIndexesSupported when it previously errored with a MongoDB version that supported it (no-need to re-fetch when it had previously succeeded).
- Update [the tooltip we show|http://example.com] when `isSearchIndexesSupported` is false to indicate that it isn't necessarily a version issue. Maybe add to the start of the tooltip: `Unable to fetch Atlas Search Indexes.`
On a quick glance it looks like there is some tech debt and side effects around how different plugins inherit and update the `isSearchIndexesSupported` value. I'm tempted to put a story points of 3 but that might make this more like a 5.
- fixes
-
COMPASS-9378 Update search indexes disabled tooltip
-
- Backlog
-