#random

Troubleshooting Import API Errors in Typesense

TLDR Atul was having trouble with import API errors, which Jason suggested might be due to a bug or missing fields. Upgrading solved the import issue but led to new problems with schemas and facet attributes.

1mo

Join the chat

Oct 11, 2023 (1 month ago)

Photo of md5-b28e2b6cff9ce32901c5ee87b38aecd5

Atul

04:14 PM

Hi Guys,
To I am trying to import data through import api.
I am getting this error "error":"[json.exception.type_error.302] type must be string, but is null","success":false} .

04:14

Atul

04:14 PM

I am not able to track the exact error.

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

04:16 PM

(For the future, could you post in #community-help)

04:16

Jason

04:16 PM

That error happens if a field is set as non-optional in the schema, and is missing the in the document

04:17

Jason

04:17 PM

But there was also a recent bug related to nested fields and this error was showing up due to the bug. You might want to also try upgrading to 0.25.2.rc4 and try again, if the above doesn't fix it

Atul

04:17 PM

But earlier I used to get error message of exact fields.

Jason

04:18 PM

It sounds more like the bug above... Could you try with that RC build?

Atul

04:19 PM

I tried it from terminal + curl.

Jason

04:19 PM

I meant the Typesense Server version

Oct 12, 2023 (1 month ago)

Atul

04:10 AM

Thanks for suggestion Jason.

I upgraded the version to 0.25.2.rc4. I was able to upload the data on the newer version.

Now I am facing another strange issue. My recent new attributes got removed from the schema :facepalm:.

Please let me know if there is any quick solution.
TIA.

04:13

Atul

04:13 AM

Another issue: my face attribute is not a facet_attribute anymore.
error: "Could not find a facet field named my__attribute in the schema."

Jason

04:12 PM

Could you try reproducing this on a new collection?

Typesense

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

Indexed 3011 threads (79% resolved)

Join Our Community

Similar Threads

Resolving Typesense 0.22.2 Syntax Error and Import Issues

John faced issues with Typesense 0.22.2 code syntax and import functionality. Jason advised to reformat the JSONL records into single lines, increase ulimit, and convert dates to int64 format manually in code. A typo in the code was also corrected.

21mo

Issues with Indexing Data using Typesense in Go

Konrad was having trouble with a "Forbidden" error using Typesense in Go when indexing data remotely. David offered multiple troubleshooting steps and suggestions. Ultimately, Konrad discovered the issue lied within the application code.

3mo

Typesense Bug Fix with `canceled_at` Field and Upgrade Concerns

Mateo reported an issue regarding the treatment of an optional field by Typesense which was confirmed a bug by Jason. After trying an upgrade, an error arose. Jason explained the bug was due to a recent change and proceeded to downgrade their version. Future upgrade protocols were discussed.

10mo

Issue with Embedding Error in Version 0.25.0.rc63

Bill reported a bug in version 0.25.0.rc63 regarding a problem with updating or emplacing a document and receiving an embedding error. This was resolved in version 0.25.0.rc65, but further discussion ensued regarding the function of 'index' in the update feature.

3mo

Trouble with Document Error in Indexing

Hauke is encountering an error during indexing with a specific field and working to provide Kishore Nallan with a reproducible example. Kishore Nallan gave troubleshooting advice, but issue not yet resolved.

3mo