New Features
Remote federated facet search
Facet search now supports searching across all shards in a network. When using thenetwork experimental feature with a leader defined, facet search calls to POST /indexes/{indexUid}/facet-search now default to remote federated search, fetching and merging results from all shards.
You can control this behavior explicitly using the new useNetwork parameter in the facet search request body.
Human-formatted database sizes and detailed internal database breakdown
The stats endpoints now support two new query parameters to give you better visibility into your index storage:showInternalDatabaseSizes: When set totrue, index stats include aninternalDatabaseSizesobject showing the size of each internal database componentsizeFormat: Set tohumanto get human-readable sizes (MiB, GiB, etc.) instead of bytes
GET /stats for global statistics.
Improvements
Reduced memory usage during indexing
Indexing memory consumption has been reduced through optimizations in prefix computation and by avoiding unnecessary deserialization. If you still experience high memory usage during post-processing, enable the--experimental-reduce-indexing-memory-usage option.
Improved GeoJSON indexing performance
GeoJSON indexing is now faster and more efficient. The optimization avoids reprocessing documents already indexed in dense cells, handling only newly added documents incrementally as they descend through the spatial cell tree.Network settings propagation
Settings changes made through individual settings subroutes are now correctly propagated to other remotes in your network.Improved Mistral provider compatibility
Fixed an issue where the chat route could fail when using Mistral as a provider.Other
Breaking changes
Remote federated facet search is now the default: When using thenetwork experimental feature with sharding enabled (leader is not null), POST /indexes/{indexUid}/facet-search calls now default to remote federated search instead of local-only search. The behavior can be controlled via the new useNetwork parameter.
Embedder timeout now tied to search cutoff: The timeout for calling an external REST embedder at search time is now based on the searchCutOffMs setting in the index, rather than using a fixed timeout. If you observe missing semantic results or HTTP 500 errors for pure semantic search after upgrading, increase the value of searchCutOffMs in your index settings.
Find more information on GitHub