Troubleshooting Alias Errors and Document Additions
TLDR David faced issues with aliasing and adding documents to their platform. Jason aided in the troubleshooting. The issue was resolved when David corrected a data type mismatch in their schema.
Nov 24, 2022 (13 months ago)
cluster id: dq56azlcmuwh2i90p
We do this because in a bulk import some documents might be successfully imported and others might fail, and we don’t want to return a failing http code just because of a few failures
Indexed 3015 threads (79% resolved)
Discussing TypeSense Setup & Documentation Improvements
Harrison faced challenges with TypeSense setup and documentation. Jason clarified reasons behind the method used for handling bulk imports and explained the HTTP response. They acknowledged Harrison's points and agreed about improving the documentation.
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.
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.
Updating Bulk Records and Resolving Typsense Issues.
Greg inquired about updating bulk records. Jason proposed using the documents/import endpoint for bulk updating, identified issues with Typesense, and provided solutions. Greg appreciated the assistance. Conversation related to the procedure was shared with Viktor.
Typesense Server Bulk Import/Upsert Issue Resolved
Adam was confused about the discrepancy between the successful responses and the actual indexed data while working with a custom WP plugin integrating with Typesense. The issue was a bug related to fetching documents in the wrong order, not a Typesense problem.