Changelog - 2026-08-30
getHealth() Never Throws, Imports Keep Progress, and collectionExists() Never Lies About Absence
Behavior Change Bug FixIn one line. Meilisearch and Typesense now both hold the ISearchConnector contract: a health probe never throws, every failed import carries partial progress, and a collection-existence check never reports absence for a failure it could not classify.
What changed
- Meilisearch
getHealth()no longer throws. A down engine used to makeping()throw instead of returningfalse. It now logs a warning and resolves{ ok: false }, like Typesense. - Typesense
importDocuments()attaches progress to every failure. AnApplicationErrorraised mid-import, a409conflict for example, now gets{ totalCount, processedCount, successCount, failCount }on itsextra.details. It is the same error, with its ownstatusCodeandmessageCodeintact. - Typesense
collectionExists()surfaces a real failure instead of reporting absence. Only a genuine not-found resolvesfalse. Any other failure reaches the caller as a sanitized503.
Who is affected
- Anyone calling
ping()orgetHealth()as a liveness probe. Both now resolve, never throw, on either engine. No action needed. - Anyone catching a Typesense
importDocuments()failure and readingerror.extra.details. It is now populated for an already-shapedApplicationErrortoo. - Meilisearch imports. Unaffected. They already merged progress onto both error shapes.
- Anyone calling Typesense
collection.exists(), directly or viaensureCollection(), while the engine is unreachable. It now throws a sanitized503instead of resolvingfalse. If your code relied onensureCollection()quietly falling back to a create on any hiccup, it now surfaces the failure, because the collection was never confirmed absent.