Upgrading and Fixing Issue with Typesense-JS Version 0.24.0
TLDR Leonardo had issues with the upgraded Typesense-JS version 0.24.0, particularly on unrecognized fields. Jason resolved it by issuing updates and adding the missing fields.
2
Feb 03, 2023 (10 months ago)
Leonardo
04:58 PMIs it possible that typesense-js ^1.5.0 is not fully typed for this new version? (fields like
enabled_nested_fields and field type object are not recognized)
Jason
04:59 PMLeonardo
04:59 PMJason
05:11 PM1.5.1-0?Leonardo
05:13 PM1
Feb 08, 2023 (10 months ago)
Leonardo
04:03 PMreturn_id paramenter of the batch import? (paremeter not typed)Jason
07:51 PMJason
08:11 PMLeonardo
08:13 PM1
Typesense
Indexed 3005 threads (79% resolved)
Similar Threads
Troubleshooting Typesense Document Update Error
Mehdi had an issue with updating Typesense documents which returned a '404 Not Found' error. Kishore Nallan after several debugging steps, discovered Mehdi was using an outdated Typesense version. The issue was resolved after upgrading Typesense.
Fixing "bad json" error in Typesense 0.24
Adam experiences "bad json" error when creating collections in Typesense 0.24. Jason identifies a typo in the docs causing the error and helps troubleshoot additional errors.
Handling Kinesis Stream Event Batching with Typesense
Dui had questions about how to handle Kinesis stream events with Typesense. Kishore Nallan suggested using upsert mode for creation/update and differentiating with logical deletion. After various discussions including identifying and resolving a bug, they finalized to introduce an `emplace` action in Typesense v0.23.
Nested Objects Issue in Firebase & Typesense Integration
Shaun encountered issues with nested objects being flattened in Typesense. Jason found the root issue and provided a solution involving updating the Firebase extension to 1.0.3.
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.