#community-help

Fixing Corrupted Documents and Upgrading Typesense Cloud Version

TLDR gab had issues with corrupted documents in Typesense Cloud. Jason suggested upgrading to version 0.24.1.rc, which resolved the issue. They also discussed CORS domain management.

7mo

Join the chat

Mar 16, 2023 (7 months ago)

Photo of md5-8be2a24edf7a95c9c74abce4b1130c3e

gab

01:17 PM

Hi,
I have a basic collection of cities in Typesense cloud.
It seems I have at least one or two corrupted documents stored.
I got this exception whenever I try to group them: TypeError: Cannot read properties of null (reading 'id')
In case I do not group them I can also see the page display less results than the results found.

Here is the multisearch result

grouped_hits: [{group_key: [], hits: [{document: null}]},…]

Here is the error locally in my machine, but the same happen in Typesense cloud, except the error comes from the minized bundle.

client.js?ab48:1 TypeError: Cannot read properties of null (reading 'id')
    at eval (SearchResponseAdapter.js?8188:58:1)
    at Array.map (<anonymous>)
    at SearchResponseAdapter._adaptHits (SearchResponseAdapter.js?8188:55:1)
    at eval (SearchResponseAdapter.js?8188:41:1)
    at Array.map (<anonymous>)
    at SearchResponseAdapter._adaptGroupedHits (SearchResponseAdapter.js?8188:40:1)
    at SearchResponseAdapter.adapt (SearchResponseAdapter.js?8188:173:1)
    at eval (TypesenseInstantsearchAdapter.js?2572:70:1)
    at Array.map (<anonymous>)
    at TypesenseInstantsearchAdapter._callee$ (TypesenseInstantsearchAdapter.js?2572:66:1)
    at tryCatch (regeneratorRuntime.js?8727:44:1)
    at Generator.eval (regeneratorRuntime.js?8727:125:1)
    at Generator.eval [as next] (regeneratorRuntime.js?8727:69:1)
    at asyncGeneratorStep (asyncToGenerator.js?af4f:3:1)
    at _next (asyncToGenerator.js?af4f:22:1)

How could I troubleshoot that ?

Thanks for help

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

04:19 PM

Could you share a screenshot of the “search parameters” section in Typesense Cloud?

gab

04:21 PM

Jason

04:24 PM

Could you DM me your cluster ID as well?

04:26

Jason

04:26 PM

Could you share the query term you used as well?

04:26

Jason

04:26 PM

(I’m essentially trying to replicate the issue on my end)

gab

04:27 PM

lanc

04:31

gab

04:31 PM

The issue can be seen also with only: queryBy: city && q=lanc
The warning won't be here but the displayed results are 2 on 4 results

Jason

04:31 PM

It seems like there’s a document that’s corrupted somehow on disk:

04:32

Jason

04:32 PM

05:33 PM

How can I manage cors domain

Jason

05:34 PM

In Typesense Cloud, we set it to * and we don’t allow that to be configurable

05:34

Jason

05:34 PM

(Mainly because it can be easily spoofed by users using direct curl requests)

gab

05:41 PM

Ok I see 👍

05:41

gab

05:41 PM

I will stick with https://typesense.org/docs/guide/data-access-control.html#scraping-protection as a beginning

Jason

05:49 PM

The upgrade is now complete. Looks like the issue is now fixed…

gab

05:49 PM

Ok perfect the migration fixed it .D

05:49

gab

05:49 PM

Thanks a lot

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

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.

12mo

Troubleshooting Issues with DocSearch Hits and Scraper Configuration

Rubai encountered issues with search result priorities and ellipsis. Jason helped debug the issue and suggested using different versions of typesense-docsearch.js, updating initialization parameters, and running the scraper on a Linux-based environment. The issues related to hits structure and scraper configuration were resolved.

131

6mo

Resolving Issues with Infix and Prefix in Query Searches

Daren struggled with searches missing values in production. Jason and Kishore Nallan offered insights and created new features to help solve the problem, which was then tested and deployed by Daren.

3mo

Handling Kinesis Stream Event Batching with Typesense

Dui had questions about how to handle Kinesis stream events with Typesense. Kishore Nallan suggested using upsert mode for creation/update and differentiating with logical deletion. After various discussions including identifying and resolving a bug, they finalized to introduce an `emplace` action in Typesense v0.23.

22mo

Resolving Multilingual Search Function in Typesense Software

Bill is having difficulty with multilingual search functionality in Typesense software. Developer Kishore Nallan suggested setting a language locale and provided a demo build. The build solution had some issues, and after multiple rounds of software updates and troubleshooting, the problem still persists.

23mo