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 (31 months ago)
sonu
06:07 PM
Jason
06:07 PMsonu
06:10 PMsonu
06:10 PMJason
06:12 PM0.21.0.rc24 is the latest versionJason
06:13 PMsonu
06:35 PMJason
06:40 PMJason
06:41 PMsonu
06:41 PMJason
06:42 PMsonu
06:43 PMdocker 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-corsJason
06:44 PMYou want to change that to typesense/typesense:0.21.0.rc24
Jason
06:44 PMsonu
06:45 PMsonu
07:17 PM0.21.0.rc24 ...gives 400error and says error: 'Field skill must be a string.',sonu
07:18 PMJason
07:21 PMsonu
07:27 PMsonu
07:28 PM
gab
08:01 PMsonu
08:07 PMJason
08:07 PMoptional: true in the collection schemasonu
08:08 PMgab
08:32 PMJason
10:12 PM
Typesense
Indexed 3005 threads (79% resolved)
Similar Threads
Issues with Schema Creation and Nested Fields
Sean encountered a problem with schema creation involving auto nested fields. Kishore Nallan suggested checking the API response for errors and adding problematic fields to the schema as optional. Sean confirmed the advice.
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.
Querying with Typesense-Js and Handling Null Values
michtio was querying using typesense-js and receiving fewer results than expected. Kishore Nallan suggested using different query parameters. Further discussion led to the handling of 'null' values and filtering syntax in the search queries. The thread ended with Jason offering migration support from Algolia to Typesense.