Upgrading Typesense to Solve Syntax Error
TLDR Ken encountered an issue with Typesense search enhancements on their site and Jason suggested an upgrade. They also discussed the possible downtime and finalized the process.
3
1
1
1
Nov 02, 2022 (14 months ago)
Ken
06:47 PM1
Ken
06:47 PMnull value for our liquidity field. I was happy to find the missing_values sort option that seems to address our need.Ken
06:47 PM{
"message": "Bad syntax for geopoint sorting field `liquidity`"
}Ken
06:48 PMsort_by param I’m using:sort_by=liquidity(missing_values: first):desc,_text_match:descKen
06:48 PMliquidity field definition (based on a GET to the collection):{
"facet": false,
"index": true,
"name": "liquidity",
"optional": true,
"type": "float"
}Ken
06:49 PM
Jason
06:50 PMKen
06:51 PM0.23.1 Docker image)Ken
06:51 PMJason
06:53 PMJason
06:53 PMKen
06:53 PMKen
06:59 PM0.23.1 to make sure I wasn’t imagining things – works exactly as described in the docs!1
Ken
07:03 PM250k records. We use a regular batch process to upsert the data, so it’s also not hard for us to recreate the collection from scratch if that’s quicker or easier. Knowing about how long will just help us schedule the this appropriately.Jason
07:04 PM1
Ken
07:05 PMJason
07:06 PMKen
07:07 PM1
Ken
07:36 PM0.23.0. Was there a change to this feature in the latest RC we should be aware of?https://typesense.org/docs/0.23.0/api/search.html#sorting-null-empty-or-missing-values
Jason
07:39 PMKen
07:40 PM0.23.1? Any major risks / downsides vs. going with the official, stable release?Jason
07:46 PMJason
07:47 PMJason
07:48 PMKen
07:51 PM0.24.0 official release?Jason
07:56 PM1
Nov 03, 2022 (14 months ago)
Ken
02:34 PMKen
02:35 PMJason
06:01 PMKen
06:43 PMKen
06:44 PM1
Typesense
Indexed 3015 threads (79% resolved)
Similar Threads
Typesense Bug Fix with `canceled_at` Field and Upgrade Concerns
Mateo reported an issue regarding the treatment of an optional field by Typesense which was confirmed a bug by Jason. After trying an upgrade, an error arose. Jason explained the bug was due to a recent change and proceeded to downgrade their version. Future upgrade protocols were discussed.
Typesense Server Crash and Counting Issue
Dan reported a server crash and counting issues with Typesense server version 0.26.0.rc1. Jason suggested an upgrade to `0.26.0.rc13` while Kishore Nallan committed to investigate the issue based on a sample dataset from Dan.
Troubleshooting 400 Error When Upgrading Typesense Firestore Extension
Orion experienced a `400` error after updating the Typesense Firestore extension, causing issues with cloud functions. They traced the issue back to a data type conflict in their Typesense collection schema after updating. With help from Jason and Kishore Nallan, they resolved the issue by recreating the collection.
Resolving Issues with Infix and Prefix in Query Searches
Daren struggled with searches missing values in production. Jason and Kishore Nallan offered insights and created new features to help solve the problem, which was then tested and deployed by Daren.
Resolving 'Sort by String Property' Error in Typesense
Ahmad was unable to sort by a string property on Typesense. Jason helped diagnose the issue, instructed the user to upgrade from their side, and enabled the sorting feature in the user's schema.