Troubleshooting Typesense 400 Error with Null Fields
TLDR sonu was encountering a 400 error due to null fields during Typesense indexing. Jason suggested upgrading to a recent version, removing null fields, and marking potentially null fields as
optional: true. gab shared a similar issue and workaround.
Jul 09, 2021 (26 months ago)
0.21.0.rc24is the latest version
docker run -i -p 8108:8108 -v /tmp/typesense-data/:/data -v /tmp/typesense-logs/:/logs typesense/typesense:0.20.0 --data-dir /data --log-dir /logs --api-key=xyz --listen-port 8108 --enable-cors
You want to change that to typesense/typesense:0.21.0.rc24
0.21.0.rc24...gives 400error and says
must be a string.',
optional: truein the collection schema
Indexed 2764 threads (79% resolved)
Troubleshooting Typesense Filter_by Parameter Issue
Sagar had trouble with the filter_by parameter in Typesense. Kishore Nallan identified issue related to indexing, which resolved part of the issue. Guidance was given for handling null values.
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.
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.
Fixing Corrupted Documents and Upgrading Typesense Cloud Version
gab had issues with corrupted documents in Typesense Cloud. Jason suggested upgrading to version 0.24.1.rc, which resolved the issue. They also discussed CORS domain management.
Typesense Feature Developments Discussed
Daniel asked about the release schedule of Typesense and the upcoming features. Kishore Nallan elaborated on the release process and confirmed the new features. They also discussed ID handling and search highlighting features. They tested one of the features successfully.