Issues and solutions regarding Typesense Updates
TLDR Yoshi faced issue in updating a field in Typesense. Jason communicated this as being due to a blocking operation by in-place schema migration and recommended using the alias method.
Oct 12, 2023 (1 month ago)
group_by. We're working on addressing that, but otherwise it's useable
Indexed 3015 threads (79% resolved)
Discussing Migration Handling for TypeSense
Jack asks how to handle "migrations" for TypeSense. Kishore Nallan recommends creating a new collection, reindexing data, then using the alias feature to swap traffic. Further clarification on blocking during schema alteration is provided.
Updating Collection Schema on Typesense Cloud Returns 408 Error
Rushil had issues updating a schema on Typesense Cloud, receiving a 408 error. Jason assisted, indicating that his cluster upgrade caused the issue, solved it, and advised to avoid similar changes in the future.
Infix Searching and Schema Updates in Typesense
Loic queried the inability to perform infix searches and update schemas in Typesense. Jason explained that default is prefix search, provided solutions for infix searching, and mentioned that a forthcoming version supports field definition updates. An upgrade was queued from backend.
Updating "sort" Property in Typesense Collection
toufiq needed to update the schema in an existing Typesense collection to include "sort" property. Jason suggested using aliasing for production environment.
Fixing Errors on Typesense Cluster
Tugay is having issues with their Typesense cluster, and Jason is trying to diagnose the problem. They have ruled out issues with the data dir and are currently considering whether the errors could be due to high concurrent writes or running bulk migrations. They plan to test with 0.24.0.rcn56 Typesense version.