<!channel> :rocket: We're very excited to announce...
# important-announcements
j
<!channel> πŸš€ We're very excited to announce the next major version of Typesense -
v26.0
today! πŸ“’ New Versioning Scheme: Starting with this release, we're dropping the
0.x.y
versioning scheme and switching to an
x.y
versioning scheme. So we're going from
0.25
⏩ to
26.0
. Read more on why here. Here are some key feature highlights: ⭐️ Built-in Conversational Search (RAG): You can now seamlessly run a semantic search and then pass the result to an LLM for summarizing the result as an answer, with pre-built integrations with OpenAI and Cloudflare hosted models ⭐️ Image Search: Search through images using text descriptions of their contents, or perform similarity searches, using the CLIP model. ⭐ Voice Search: Capture and send query via voice recordings -- Typesense will transcribe (via Whisper model) and provide search results. ⭐️ JOINs: Connect one or more collections via common reference fields and join them during query time. This allows you to model SQL-like relationships elegantly. ⭐️ Search Personalization using historical search queries for each user. ⭐️ Analytics: Ability to track queries that don't produce hits and ability to track counts of document-level analytics (eg: clicks, views, etc) to improve search relevance. ⭐️ Sorting based on Filter Score: You can now use
_eval
in
sort_by
and assign scores to records that match particular filters, to boost or bury a set of records together. the filter expression. ⭐️ Stemming: Allows handling common word variations of the same root word. This is helpful for different word-forms of the same root word (eg: plurals / singular). Eg: Searching for
walking
, will also return results with
walk
,
walked
,
walks
, etc when stemming is enabled. ⭐️ Prefix Filtering: During filtering, you can now query on records that begin with a given prefix string. Eg:
company_name: Acm*
will return names that begin with
acm
. ⭐️ Stop Words: Specify a list of common words (e.g.
a
,
am
,
the
,
are
, etc.) that should be excluded from the indexing and search process to improve search relevance and performance. ⭐️ Curate / Override by Tags: You can tag override rules with tags and then trigger curation by referring to the rule by the tag name directly at search time. There are several more enhancements and important bug fixes in this release. Read the full changelog here. A BIG thank you to everyone who contributed ideas, code and feedback that helped shape this release πŸ™ Some interesting stats πŸ“ˆ β€’ We now serve 3 BILLION searches per month on Typesense Cloud. β€’ Typesense's Docker Image has been downloaded 13M+ times. β€’ Typesense's GitHub repo now has 17.5K+ stars.
πŸ™ŒπŸ½ 1
πŸš€ 35
clap 20
πŸŽ‰ 64
πŸ‘€ 7
πŸ™Œ 5
πŸ™ŒπŸ» 1
❀️ 11
z
Hey guys, amazing work as usual! Great to see Joins out, definitely my most anticipated feature for this release, thanks for all the hard work. Are the
facet_by
and
query_by
parameters for referenced fields tracked on the roadmap still, hoping these weren't 86ed due to complexity?
a
I have laughed every release the last few releases of Typesnese. The progress is simply surreal. No nonsense, straight growth. I hope Typesense Cloud is also serving your personal finances to the same degree!
πŸ™ 1
I mean 3 billion searches is on par with DuckDuckGo.
πŸ˜„ 1
j
Thanks Alexander!
@Zac Evans We did have to defer facet_by and query_by support in JOINs to a later release, since it involved a non-trivial amount of work. But sort_by is already supported
πŸ‘ 1
c
WAT, amazing work.
πŸ™ 1
r
So excited about this release! So many interesting things I can’t wait to try. But also LOVE to see improvements to the basics, like stemming! Finally!
πŸ™Œ 1
j
RAG, stemming and stop words is HUGE
πŸ™Œ 1
s
Great work on yet another release! Quick question, does
/conversations/models
supports custom OpenAPI domain like in
/collections
?
πŸ™Œ 1
j
No that endpoint does not support custom OpenAPI domain yet. Could you create a GitHub issue for this?
πŸ‘ 1