#community-help

Resolving "Bad JSON" Error during Typesense Collection Creation

TLDR Cassandra had an error creating a Typesense collection. Kishore Nallan resolved this by suggesting to input JSON data directly, not as a file.

17mo

Join the chat

Apr 05, 2022 (17 months ago)

Photo of md5-3cbb7fe1dc4e108829c749183bbecfb4

Cassandra

07:49 AM

Hello, I have a problem when I try to create a collection the following error is returned: {"message": "Bad JSON."} Yet I made a copy and paste of the official Typesense guide.

07:50

Cassandra

07:50 AM

curl "http://workmetadata.francecentral.cloudapp.azure.com:5005/collections" -X POST -H "Content-Type: application/json" -H "X-TYPESENSE-API-KEY: keyhdh" -d collection.json

07:51

Cassandra

07:51 AM

Here is the command line I run and my file collection.json

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

07:54 AM

👋 Can you please post the collection.json as text here? Let me try, maybe there are some non-visible bad characters that's not valid json.

Cassandra

07:56 AM

{
"name": "books",
"fields": [
{"name": "title", "type": "string" },
{"name": "authors", "type": "string[]", "facet": true },

{"name": "publication_year", "type": "int32", "facet": true },
{"name": "ratings_count", "type": "int32" },
{"name": "average_rating", "type": "float" }
],
"default_sorting_field": "ratings_count"
}

Kishore Nallan

07:59 AM

This works for me locally:

curl -k "" -X POST -H "Content-Type: application/json" \
      -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" -d '{
    "name": "books",
    "fields": [
      {"name": "title", "type": "string" },
      {"name": "authors", "type": "string[]", "facet": true },
      {"name": "publication_year", "type": "int32", "facet": true },
      {"name": "ratings_count", "type": "int32" },
      {"name": "average_rating", "type": "float" }
    ],
    "default_sorting_field": "ratings_count"
  }'

08:00

Kishore Nallan

08:00 AM

The guide uses inline JSON bodies like this and not -d collection.json -- if you can tell me where exactly in the guide we use this format, I can also check that.

Cassandra

08:02 AM

I copy paste your command line and it works. Thank you very much

Kishore Nallan

08:02 AM

👍

Typesense

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

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Issues with Importing Typesense Collection to Different Server

Kevin had problems migrating a Typesense collection between Docusaurus sites on different machines. Jason advised them on JSONL format, handling server hosting, and creating a collection schema before importing documents, leading to successful import.

1mo

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.

6mo

Troubleshooting Typesense Connection Issue and Data Retrieval

Felix encountered issues connecting to a server-created typesense and retrieving data collections. Kishore Nallan and Jason provided guidance, highlighting errors in the original code and suggesting changes to the URL and curl command.

20mo

Sorting Results in Typesense and Handling Errors

Ramees asks about sorting results by distance in Typesense, entering a list of strings as a field, and resolving an error with `fields` format. Kishore Nallan assists with these issues and advises on storing timestamps and proper authentication.

26mo

Resolving Issues with Scoped API Keys in Typesense with Golang

Suvarna had problems with generating and using scoped API keys in Typesense with Golang. Several bugs misleading the user were found and fixed by Kishore Nallan.

158

24mo