v1.52.0
Introduces /tasks/stream and /batches/stream SSE routes for live engine connections, reducing network load through push-based task and batch status updates. Also improves search speed by converting O(n) operations to O(1) for large result sets, and fixes duplicate pins in federated search.
✨ Enhancement
- Introduce the
/tasks/streamand/batches/streamSSE routes by @Kerollmops in #6533
This experimental feature allows establishing a live connection to the engine, avoiding the need to implement long polling and instead letting the engine provide new tasks, batches, and batch progress in a push-based manner. Using this route can drastically reduce network load when retrieving the status of a Meilisearch instance. - Speed up the search speed a bit more by @Kerollmops in #6542
We improve the search speed when it comes to formatting the documents by making anO(n)operation, wherenis the number of retrieved documents, become anO(1)operation. This improvement can significantly increase search speed when requesting a large (> 20) number of documents.
🪲 Bug fixes
- Fix duplicate pins in federated search by @dureuill in #6543
- Skip the settings when nothing changes by @Kerollmops in #6544
Source: original entry ↗
More from Meilisearch
Follow Meilisearch to get its new changes in your feed and email digest.
v1.55.0: Dynamic search rule preview and facet performance details
Added support for inline dynamic search rules that preview rule effects on individual queries, and enhanced performance details to show facet distribution computation timing. The inlineRule parameter allows applying temporary rule overrides during search without persisting them, useful for preview UIs.
Avoid panic in highlighting with safer indexing
Replaced unsafe bracket indexing with get method and added None recovery in the highlighting logic to prevent panics. This improves stability when processing edge cases in search result highlighting.
Support edge case with 4G+ rules in DSR index
Added support for an edge case where the DSR index contains four or more rules, improving stability for complex rule configurations.