Errors When Querying Non-existent Indexes
I renamed the first index I created when testing out the feature so it wasn't default, and spent quite a bit of time debugging why my queries were returning no documents. As it turns out it the default index that it queries if not defined is "default", but that index didn't exist. Instead of throwing an error about querying a non-existent index, it just returned an empty array which was very frustrating
Alex
shared this idea
This work is under review and research.
-
Andrii Hrachov
commented
Upvote. We had numerous incidents on production because of that.
On the good side, now we have canary testing, and empty responses alerts, but all of this could be avoided.
-
[Deleted User]
commented
I encountered the same issue. When an index does not exist, I'd prefer to get an error/warning message than an empty array. It took me some time to realize I'd misspelled the index name.