#community-help

Resolving Error with JSON Boolean Field

TLDR GM faced an error with a JSON boolean field, Jason suggested checking the field definition. After using curl commands, GM realized the issue and discussed improving error messages.

3mo

Join the chat

Jun 20, 2023 (3 months ago)

Photo of md5-9f364f57af6f71faaf6ea963342ef3f6

GM

06:44 PM

in my JSON document i have field like below and this is my search parameters and still getting error like this .this is boolean value..what we are missing here

Image 1 for in my JSON document i have field like below and this is my search parameters and still getting error like this .this is boolean value..what we are missing here

Image 2 for in my JSON document i have field like below and this is my search parameters and still getting error like this .this is boolean value..what we are missing here

Image 3 for in my JSON document i have field like below and this is my search parameters and still getting error like this .this is boolean value..what we are missing here

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

07:31 PM

Could you check the field definition for that field in the collection schema? It sounds like it might be set to a string

GM

07:34 PM

okay

07:41

GM

07:41 PM

07:42

GM

07:42 PM

Jason

Jason

07:44 PM

Hmm, could you try replicating the issue with this set of curl commands by adapting it to your schema and one sample record: https://gist.github.com/jasonbosco/7c3432713216c378472f13e72246f46b

07:44

Jason

07:44 PM

And share that adapted snippet with me?

GM

07:46 PM

i will dm you..thanks jason

Jun 21, 2023 (3 months ago)

GM

05:00 PM

Jason this issue has been fixed. In the query field added boolean field. thats why we got that error. we can add more exact error message for this scenarios in future releases

Jason

05:34 PM

Ah I missed that too from the error message. We’ll improve it

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2776 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

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.

7mo

Filtering by Boolean in JS SDK

Gustavo had trouble filtering by boolean in JS SDK. Kishore Nallan suggested using 'bool' instead of 'boolean', which resolved the issue.

4mo

Import Failure Issue with Booleans in Schema

Todd faced issues with document import due to booleans in the schema. Kishore Nallan helped diagnose the problem, which was solved by explicitly declaring the boolean in the schema.

4mo

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.

4mo

Understanding Document ID Fields and Rectifying Duplicate Document Error

John queried about understanding document ID fields and fixed a duplication issue with guidance from Jason. They discovered a bug preventing document deletion due to a URL encodable character, with John opening a GitHub issue for it.

19mo