Outline: [Article Title]

Keyword: [Enter Targeted Keyword]

Keyword MSV: [Enter Targeted Keyword’s Monthly Search Volume]

Author: [Enter Author Name]

Due Date: [Enter Due Date]

Publish Date: [Enter Desired Publish Date]

User Persona: [Enter Targeted Reader and/or User Persona]


This section includes all the details of the API Endpoints available in Typesense and all the parameters you can use with them.

What is new on Typesense v0.22.2?

This version, v0.22.2, fixes some critical bugs in the previous version, v0.22.1. As a result, some of the most notable bug fixes in this version are:

  • Fixed edge cases in large document imports where imports would sometimes hang mysteriously or end prematurely.
  • Fixed a document with duplicate IDs that was being imported as two separate documents as part of an import upsert batch.
  • Fixed fields with names containing a regular expression that act as an auto type rather than respecting the schema type.
  • A few edge cases in multi-field searching have been addressed, particularly those involving field weighting and boosting.
  • Fixed the issue where deletion of collections with slashes or spaces in their names did not work: you can now URL encode the names while calling the API.
  • Documents were being duplicated as a result of an edge case in the exporting of documents using a filter by condition.
  • Allow dict/hashmap fields in documents when the collection schema contains a wildcard auto (.*) field.
  • Better validation + handling of unexpected data errors during indexing.
  • Fixed a rare but critical bug that manifested during document updates that had performance implications.

Click on the link below to learn more about the most recent updates to Typesense’s latest version.

New features released in the recent version of Typesense

Lots of changes happened from previous version of typesense to latest ones.The changelog breakdowns below summarizes all of the changes between v0.21.0 and v0.22.2.

  • Customizable word separators: during schema creation, define a list of special characters using the token separators configuration. These characters, along with space and new-line characters, are then used as word separators.
  • Index and search special characters: During schema creation, use the symbols to index configuration to specify a list of special characters that will be indexed as text.

Click on the following links to learn more about all of the changes in the latest release of typesense.

Deprecated features of Typesense

  • After upgrading your Typesense server to v0.22, the data directory can no longer be used with the v0.21.0 binary. As a result, before upgrading, please take a snapshot/backup of the data directory.
  • The drop tokens threshold and typo tokens threshold parameters are now set to 1. If you were relying on the previous defaults (10 and 100, respectively), please explicitly set these parameters.
  • The minimum word length for 1-character typo correction has been raised to four. Similarly, the minimum length for a 2-character typo has been increased to 7. This has helped to reduce the number of false fuzzy matches. These default values can be modified using the min len 1typo and min len 2typo parameters.

Visit the link below to learn more about the deprecated feature from Typesense’s latest releases.

Closing

Typesense was built with several distinctive features primarily aimed at making the developer’s job easier while also giving customer as well as user the ability to provide a better search experience as possible.This article may have been entertaining as well as instructive in terms of how to install typesense from the ground up on a variety of platforms. Join Aviyel’s community to learn more about the open source project, get tips on how to contribute, and join active dev groups.

Call-to-Action

Aviyel is a collaborative platform that assists open source project communities in monetizing and long-term sustainability. To know more visit Aviyel.com and find great blogs and events, just like this one! Sign up now for early access, and don’t forget to follow us on our socials!