Improving Error Handling in Typesense Non-Compliant Documents
TLDR micha suggested enhancing error responses for non-compliant documents in typesense and suggested an exception property in the PHP client. Jason instructed them to document this in a Github issue.
May 11, 2022 (20 months ago)
a) there would then also be a way to get this specific data as properties of the requestmalformed exception in the php client and maybe even
b) if it would be possible to accept the document but have it not indexed (not sure how good this suggestion really is :D)
Indexed 3005 threads (79% resolved)
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.
Adding and Updating Collections in Typesense Server
sonu asked about methods to add and update collections in a Typesense server. Jason advised that documents can be added individually or in bulk, and updates can be batched using the import function, even with a small React app with a MySQL database.
Cold Start Problem with Dynamic Collections
Adrian reported cold start issues with dynamic collections. Jason suggested using wildcard `*` for query_by parameters, upgrading to `0.25.0.rc34`, and clarified conventions. Adrian's issues were resolved but they reported a limitation that will potentially be addressed.