Issues with Typesense Import API Document Indexing
TLDR Morgan experienced inconsistent document indexing using the Typesense Import API. Jason clarified that Typesense returns a success: true or false for each record in the batch import call.
Jan 12, 2022 (24 months ago)
Morgan
11:04 PMAction: "upsert"
BatchSize: 100I have 5 goroutines sending around 10000 documents and each request has about 500 documents. Each of them has unique key so there should be 10k document in my collection. But what I have found is the number of document is always smaller than what I actually sent, around 7k. And when I reduce the request size from 500 to 200, there are more documents show up in cluster. But I don’t see any feedback from Typesense if any of the batch was not successful.
Is it safe to say when importing, TS will not send whether the documents in the request has been successfully indexed? If so, what can I do to make sure the documents I send will be indexed?
Jason
11:35 PM
Typesense
Indexed 3011 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.
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.
Resolving Content Indexing Problems with Typesense
Maik experienced issues with indexing content in typesense. Kishore Nallan and Md suggested checking the import response and added error handling to identify and address the errors. Maik successfully located the issue.