#community-help

Troubleshooting Alias Errors and Document Additions

TLDR David faced issues with aliasing and adding documents to their platform. Jason aided in the troubleshooting. The issue was resolved when David corrected a data type mismatch in their schema.

13mo

Join the chat

Nov 24, 2022 (13 months ago)

Photo of md5-07c4f1bfa85fc4a2759ba7302f0b86da

David

04:37 PM

is something wrong with aliasing atm?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

04:38 PM

Every cluster is independent and we don’t auto upgrade clusters. Could you share you cluster ID?

David

04:44 PM

example page that doesn't load any results https://beta.hem.com/en-eu/furniture/chairs-and-stools

cluster id: dq56azlcmuwh2i90p

Jason

04:45 PM

Looking at the network requests, made on that page, I see calls to Typesense successfully returning results…

David

04:45 PM

no wait, seem to be unrelated. ignore me

04:46

David

04:46 PM

yes i see. it's something I do when adding results

Jason

04:46 PM

I also see search requests coming into your cluster

David

04:46 PM

ok, thank you for chekcing ❤️

05:50

David

05:50 PM

Jason sorry, could you see if there are any errors in adding documents?

Jason

05:57 PM

I don’t see anything in the logs…

David

05:57 PM

Ok, thank you for verifying / checking

Jason

05:58 PM

Are you seeing any errors on your side with writes?

David

05:58 PM

Not that I can see, but my logging on CI (Gatsby Cloud) is practically non-existent

Jason

05:59 PM

Ah, are you able to run it locally may be, to check for any errors? The kind of errors I’d see on my side are any unhandled JSON parsing issues for eg

06:00

Jason

06:00 PM

But if it’s a handled schema validation error for eg, we only return that in the API response

David

06:00 PM

its' more that we usually have ~1200+ documents, but now there's only 172

06:01

David

06:01 PM

just in time for Black Friday :partying_face:

06:01

David

06:01 PM

haha

06:01

David

06:01 PM

classic

09:19

David

09:19 PM

… and it's working! It had to do with my schema, where I had the price as int32, and I was sending it floats as the price was now discounted. I didn't see any errors though when sending as JSONL, but adding documents directly as a normal array showed the errors.

Jason

09:21 PM

Ah! Glad you found the issue. Btw, the import endpoint which accepts JSONL will always return a 200, you need to look at the response body for the actual error.

We do this because in a bulk import some documents might be successfully imported and others might fail, and we don’t want to return a failing http code just because of a few failures

David

09:21 PM

Makes perfect sense, just hadn't encountered it before and it took a while to figure out where to look (is it Gatsby? Shopify? Typesense? Etc

09:23

David

09:23 PM

Thank you for helping out, even on Thanksgiving. LMK if you want a nice discount on any Hem furniture hehe. https://beta.hem.com/en-us

Jason

09:24 PM

Haha! Happy to help 🙂

Happy Thanksgiving!

Typesense

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

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Discussing TypeSense Setup & Documentation Improvements

Harrison faced challenges with TypeSense setup and documentation. Jason clarified reasons behind the method used for handling bulk imports and explained the HTTP response. They acknowledged Harrison's points and agreed about improving the documentation.

24mo

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

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.

14mo

Updating Bulk Records and Resolving Typsense Issues.

Greg inquired about updating bulk records. Jason proposed using the documents/import endpoint for bulk updating, identified issues with Typesense, and provided solutions. Greg appreciated the assistance. Conversation related to the procedure was shared with Viktor.

13mo

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.

7mo