Debugging Import Failures in Example Search Application
TLDR satish was having trouble getting search results in an application. Kishore Nallan explained that all endpoints are synchronous and suggested checking the import response for errors. The issue was resolved when satish found a mistake in the sorting field name.
1
Apr 05, 2022 (19 months ago)
satish
09:21 AMKishore Nallan
09:30 AMHit the /collections endpoint to see the count of documents and other collection metadata.
satish
09:33 AMKishore Nallan
09:34 AMKishore Nallan
09:39 AMsatish
11:22 AM1
Typesense
Indexed 2779 threads (79% resolved)
Similar Threads
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.
Troubleshooting Indexing Duration in Typesense Import
Alan asked about lengthy indexing times for importing documents to Typesense. Jason suggested various potential causes, including network connectivity and system resources. They later identified the problem to be an error in Alan's code.
Revisiting Typesense for Efficient DB Indexing and Querying
kopach experienced slow indexing and crashes with Typesense. The community suggested to use batch import and check the server's resources. Improvements were made but additional support was needed for special characters and multi-search queries.