Bug in Using Import-Documents Endpoint
TLDR Dan reported a bug when using the import-documents with an upsert to update documents while Cory experienced the same. Kishore Nallan offered a solution through a release candidate (RC) build after identifying the data edge case.
Aug 31, 2022 (16 months ago)
Dan
01:03 PM400
with some payloads - and there is no further information given. this only happens in one environment, on our staging env (with same schema and doc) it imports correctly. A minimal document of an id and one field always triggers this.Kishore Nallan
01:03 PMDan
01:03 PMDan
01:03 PMKishore Nallan
01:03 PMDan
01:04 PM"{\"message\": \"Bad request.\"}",
Dan
01:04 PM{"Connection" "close",
"access-control-allow-origin" "*",
"content-type" "application/json; charset=utf-8",
"transfer-encoding" "chunked"}
Kishore Nallan
01:05 PMDan
01:05 PMDan
01:05 PMKishore Nallan
01:06 PMDan
01:07 PMSep 10, 2022 (15 months ago)
Cory
02:35 PMBad request
and can’t see any noticeable difference between the payloads that succeed and fail. Though they do seem to be somewhat consistent.Kishore Nallan
02:37 PMTypesense
Indexed 3005 threads (79% resolved)
Similar Threads
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.
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.
Resolving Typesense v0.22.0 Import Issues
Anton encountered issues importing documents in batches using Typesense v0.22.0. Kishore Nallan suggested using atomic import and proposed a debug build. After multiple trials, they were able to reproduce and fix the issue. Anton confirmed the solution was working.
Working with Typesense SDK and Addressing Import Issues
Jacob was having issues with importing and indexing documents using Typesense SDK. After discussing with Jason, the user discovered the `emplace` action was ideal for their parallel processing requirement.
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.