<!channel> v28.0 of Typesense Server is now genera...
# important-announcements
j
<!channel> v28.0 of Typesense Server is now generally available πŸŽ‰ Some key highlights: βœ… Union feature lets you merge multi_search results βœ… Dictionary-base stemming βœ… Sort by random order, decay functions, around a pivot value βœ… Ability to set fixed bucket sizes for text_match tie breaking βœ… New Geo polygon data type for geo search βœ… Faceting performance improvements βœ… Several improvements to JOIN-related features. Here's the full changelog: https://github.com/typesense/typesense/releases/tag/v28.0 As usual, a big thank you to everyone who has contributed ideas, questions, feedback and code to this release! πŸ™Œ
❀️ 2
πŸŽ† 9
πŸ‘€ 8
πŸ₯­ 8
πŸ‘πŸΎ 1
party parrot 11
πŸŽ‰ 81
πŸ‘ 21
πŸš€ 20
s
Awesome work guys, thanks!
πŸ™ 1
πŸ‘ 1
s
very nice update! πŸ’ͺ
πŸ™Œ 1
l
Some useful stuff in there, thanks!
πŸ™Œ 1
s
can updates be down in place with no downtime?
l
you're great folks!, just needed some features you've added! :)
πŸ™Œ 1
j
Great to hear that! πŸ™Œ
@Shane Jordan If you have high availability enabled, then there won’t be downtime: https://cloud-help-center.typesense.org/article/10-high-availability If you don’t have HA enabled then there will be downtime proportional to the size of your dataset, but the update can still be done in-place.
s
yes i have HA! thanks for clarification. i'll update now. πŸ™‚
s
Do you have more details on the faceting performance improvements? On the link above it isn't more specific than that.
j
In some synthetic benchmarks we did, we saw a 20-25% improvement in
search_time_ms
for queries that used
facet_by
at high concurrency
s
In some situations we have to force exhaustive strategy (reduces query time from 5 seconds to 500 ms). Should we re-evaluate that in V28?
j
Exhaustive search is always going to be expensive, because it does a bunch of things that you might not necessarily need. In many cases, just increasing max_candidates to a high value solves the issue
πŸ‘ 1
e
Thanks for adding the sorting around a pivot value! This will greatly simplify the use-case we suggested it for now 😁
πŸ™Œ 1