#community-help

Resolving Issues with JSON Returns in Create() Calls

TLDR Krish was having trouble getting a JSON return from a create() call. Kishore Nallan and Jason suggested solutions but the issue was ultimately resolved by Krish finding a typo in their code.

10mo

Join the chat

Dec 14, 2022 (10 months ago)

Photo of md5-7dff5651efcba5c9cdfac93918dc7eeb

Krish

05:25 AM

Question: Is there a way to confirm if a create() (ie: index a single doc) call is successful? I was thinking it'll return something in json, but it doesn't.

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

05:26 AM

201 status code

05:27

Kishore Nallan

05:27 AM

It does return the document back in JSON as well

Krish

05:27 AM

i see it getting indexed but not getting the json

Kishore Nallan

05:28 AM

What client are you using?

Krish

05:30 AM

it's nodejs

Kishore Nallan

06:22 AM

If there is an issue, I believe an exception is thrown.

Krish

06:25 AM

Ideally I'd expect that. But I don't see anything returned. A curl invocation returns the record, but in node it doesn't. Let me play around for some time.

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

06:26 AM

The node client returns a promise after async API calls, so you’d have to await the promise to get the API results

06:28

Jason

06:28 AM

Here’s an example: https://github.com/typesense/typesense-js/blob/master/doc/examples/server/documents.ts

Krish

06:40 AM

This is exactly how I coded it. When I didn't see the json I put it in a promise and I still don't see it :) I'll look for issues in code again..

Jason

01:48 PM

Hmm, could you share a minimal reproducible snippet I can run locally to replicate the issue?

Krish

01:50 PM

Thank you Jason. But I fixed it. Sorry I wasted time here, it was a typo in my code.

Jason

01:51 PM

Phew, glad the issue is resolved!

Krish

01:52 PM

Sorry man..

Jason

01:52 PM

No worries! Happy to help

Typesense

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

Indexed 2779 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

Typesense Server Bulk Import/Upsert Issue Resolved

Adam was confused about the discrepancy between the successful responses and the actual indexed data while working with a custom WP plugin integrating with Typesense. The issue was a bug related to fetching documents in the wrong order, not a Typesense problem.

5mo

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

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

Resolving Typesense v0.22.0 Import Issues

Anton encountered issues importing documents in batches using Typesense v0.22.0. Kishore Nallan suggested using atomic import and proposed a debug build. After multiple trials, they were able to reproduce and fix the issue. Anton confirmed the solution was working.

25mo