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.
2
1
Mar 16, 2023 (7 months ago)
gab
01:17 PMI 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
Jason
04:19 PMgab
04:21 PMJason
04:24 PMJason
04:26 PMJason
04:26 PMgab
04:27 PMlanc
gab
04:31 PMThe warning won't be here but the displayed results are 2 on 4 results
Jason
04:31 PMJason
04:32 PMJason
04:32 PMgab
04:32 PMJason
04:32 PM0.23.0.rc27
… and I vaguely remember fixing some related issues in more recent builds. Can we upgrade you to the latest 0.24.1.rc?gab
04:33 PMJason
04:34 PMhttps://typesense.org/docs/0.23.1/api/
https://typesense.org/docs/0.24.0/api/
0.24.1 just has some bug fixes from 0.24.0
gab
04:38 PMThanks
Jason
04:41 PMgab
05:24 PMJason
05:33 PMJason
05:33 PMgab
05:33 PMgab
05:33 PMgab
05:33 PMJason
05:34 PM*
and we don’t allow that to be configurableJason
05:34 PMgab
05:41 PMgab
05:41 PM1
Jason
05:49 PMgab
05:49 PM1
gab
05:49 PM1
Typesense
Indexed 2779 threads (79% resolved)
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.
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.
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.
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.
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.