This release contains important new features, performance improvements and bug fixes.

New Features

• Natural Language Search: Typesense can now detect user intent in natural language queries and convert them into structured search queries using LLMs. This allows a user query like q: A Honda or BMW with at least 200 hp to be understood and executed by Typesense as filter_by: make:[Honda, BMW] && engine_hp:>=200 automatically. (Docs)
• Dynamic Sorting in Overrides: Typesense now supports dynamic sorting rules within override definitions, similar to dynamic filtering. This enables query-dependent sorting of results through override rules (Docs).
• Filter multiple properties within a nested array of objects: You can now scope filter expressions to a specific nested object within an array field (Docs).
• Streaming support for conversations: responses from LLM APIs are now directly streamed, allowing you to build interactive chat experiences. (Docs).
• Support adding meta fields to query analytics documents: You can now pass the filter_by search parameter and a new analytics_tag search parameter that you can set to any string you need, to be stored with your popular and no-hits queries. This gives you additional context around the search. (Docs).
• You can now fetch JOIN reference fields in the GET document API (Docs)

Enhancements

• Improved group-by performance and resource usage, especially when high cardinality fields (like productId) are used for grouping.
• Improved performance of numeric range queries.
• Return uniform API response structure when union: true is set, regardless of number of collections queried.
• Ability to customize RocksDB parameters like write buffer sizes for better performance. (Docs).
• Support for filtering with nested object fields in overrides.
• Ability to do image search using user-uploaded images at runtime (Docs).
• Support for configuring the max group_limit via a new server-side parameter called max-group-limit (Docs).
• Support caching for remote query embeddings via embedding-cache-num-entries server-side parameter (Docs).
• Support for sorting when doing a one-to-many JOIN (Docs).
• Support for bucketing on vector distance (Docs).

Bug Fixes

• Fixed a few bugs related to updates of deeply nested field values.
• Fixed phrase search queries being stemmed.
• Respect field-level tokenization config in filters.
• Fixed facet sum being wrong when negative values are added.
• Fixed vector query parsing with backticks escaping special characters.
• Improve reliability of joins during imports.
• Fixed broken cache-num-entries server side parameter.
• Exclude x-typesense-user-id from cache key to make cache global.
• Fixed import of large stemming dictionaries.
• Fixed auth token refreshing problem for GCP-based embedding generation.
• Fixed vector search not working reliably with 3 sort_by fields.
• Fixed a bug caused by using flat_search_cutoff along with filtering for vector search.
• Tweak rank computation for fusion scoring - two keyword search results with same text match score should have the same keyword search rank.
• Improved reliability of CLIP embeddings under high concurrency.
• Fixed a bug with collection truncation, requiring unnecessary parameters.
• Fixed a bug where the alter operations endpoint was returning the incorrect document counter.
• Fixed a bug where analytics counters only worked with int32 fields.

Deprecations / behavior changes

• For group_by queries, the found value returned in the response is no longer an exact number. It's an approximation of the number of groups found, and is guaranteed to be within 2% of the actual number of groups found.

Upgrading

Before upgrading your existing Typesense cluster to v29.0, please review the behavior changes above to prepare your application for the upgrade.

We'd recommend testing on your development / staging environments before upgrading.

Typesense Cloud

If you're on Typesense Cloud:

1. Go to https://cloud.typesense.org/clusters.
2. Click on your cluster
3. Click on "Cluster Configuration" on the left-side pane, and then click on "Modify"
4. Select a new Typesense Server version in the dropdown
5. Schedule a time for the upgrade.

Self Hosted

If you're self-hosting Typesense, here are instructions on how to upgrade: https://typesense.org/docs/guide/updating-typesense.html#typesense-self-hosted

Downgrading

Once you upgrade to v29 of Typesense Server, you can only downgrade back to: v28, v27 or v26.

Documentation

View the complete API documentation for this release here: https://typesense.org/docs/29.0/api/