Ingesting JSON Data and UnhandledPromiseRejectionWarning Error.
TLDR vikram had an issue concerning ingestion of data from local sources and facing error. Jason helped them realize the error was due to an existing collection, and they fixed the problem.
Oct 23, 2022 (14 months ago)
vikram
06:08 AMKishore Nallan
07:49 AMvikram
08:24 AMKishore Nallan
08:34 AMKishore Nallan
08:35 AMvikram
08:35 AMKishore Nallan
08:36 AMvikram
08:38 AMKishore Nallan
08:39 AMvikram
08:43 AMvikram
09:32 AMvikram
09:32 AMartist
already exists.at ObjectAlreadyExists.TypesenseError [as constructor] (/media/sf_Backup/vikram/typesense-instantsearch-demo/node_modules/typesense/lib/Typesense/Errors/TypesenseError.js:23:28)
at new ObjectAlreadyExists (/media/sf_Backup/vikram/typesense-instantsearch-demo/node_modules/typesense/lib/Typesense/Errors/ObjectAlreadyExists.js:25:42)
at ApiCall.customErrorForResponse (/media/sf_Backup/vikram/typesense-instantsearch-demo/node_modules/typesense/lib/Typesense/ApiCall.js:337:21)
at /media/sf_Backup/vikram/typesense-instantsearch-demo/node_modules/typesense/lib/Typesense/ApiCall.js:195:98
at step (/media/sf_Backup/vikram/typesense-instantsearch-demo/node_modules/typesense/lib/Typesense/ApiCall.js:33:23)
at Object.next (/media/sf_Backup/vikram/typesense-instantsearch-demo/node_modules/typesense/lib/Typesense/ApiCall.js:14:53)
at step (/media/sf_Backup/vikram/typesense-instantsearch-demo/node_modules/typesense/lib/Typesense/ApiCall.js:18:139)
at Object.next (/media/sf_Backup/vikram/typesense-instantsearch-demo/node_modules/typesense/lib/Typesense/ApiCall.js:14:53)
at fulfilled (/media/sf_Backup/vikram/typesense-instantsearch-demo/node_modules/typesense/lib/Typesense/ApiCall.js:5:58)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
Jason
01:10 PMvikram
01:30 PMTypesense
Indexed 3015 threads (79% resolved)
Similar Threads
Troubleshooting Typesense Docsearch Scraper Setup Issue
Vinicius experienced issues setting up typesense-docsearch-scraper locally. Jason identified a misconfiguration with the Typesense server after checking the .env file, and recommended using ngrok or port forwarding for development purposes. Vinicius successfully resolved the issue with port forwarding.
Unresolved High-Volume Write Issue in Typesense
Greg experienced issues with Typesense where it became unresponsive during high-volume write operations. Jason and Kishore Nallan suggested several solutions, but the issue remained unresolved. They suspect that the problem occurs when concurrent writes are happening to the same collection.
Large JSONL Documents Import Issue & Resolution
Suraj was having trouble loading large JSONL documents into Typesense server. After several discussions and attempts, it was discovered that the issue was due to data quality. Once the team extracted the data again, the upload process worked smoothly.
Issue Resolution and Upgrade Problems in Typesense Version 0.26rc16
Ankit reported an issue with Typesense, which was addressed by Kishore Nallan and Jason. However, Ankit experienced difficulties while trying to upgrade, with the server status showing as "Not ready or lagging" 503. The resolution remains incomplete.
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.