Resolving Document Upsert Error
TLDR S had an error while trying to upsert a document. Kishore Nallan suggested using a different build (0.12.0 rcs13
). Issue was resolved but S had other issues relating to "id" usage and INI file parsing, awaiting Kishore Nallan response for these.
1
Oct 10, 2021 (25 months ago)
S
10:58 AM# document being upserted
{
...
"mobilities_stringarr_yesindex_nofacet": [],
...
}```
# collection field{
"facet": false,
"index": true,
"name": ".*_stringarr_yesindex_nofacet",
"optional": true,
"type": "string[]"
},
# the error{
"message": "Type of field
mobilities_stringarr_yesindex_nofacet
is invalid."}```
Kishore Nallan
10:59 AMS
11:01 AMI have added it now.
Kishore Nallan
11:02 AMKishore Nallan
11:03 AMS
11:03 AMShall I use an rc?
Kishore Nallan
11:03 AM0.12.0 rcs13
?Kishore Nallan
11:03 AMS
11:03 AM<https://hub.docker.com/layers/typesense/typesense/0.22.0.rcs13/images/sha256-4957b3da9ad910bed57470a742c6eb8058566c9887d9156d4b726800eb2ec2af?context=explore|0.22.0.rcs13>
1
S
09:01 PMS
09:14 PMโข I suspect this issue to be new to 0.22: I cannot do
query_by: id
(anymore)Collection schema cannot contain a field with name
id. Ignoring field.
โข I suspect this issue to be general to TS, or only the ini-parser. Max length for the master token is approx. 128, this is not documented.
'config file cannot be parsed'
warning occurs in logs, limitation may hypothetically not be present when using env varsOct 11, 2021 (25 months ago)
Kishore Nallan
01:37 AM2. Can you post a sample INI file here that I can test locally?
Typesense
Indexed 2776 threads (79% resolved)
Similar Threads
Threading Problem During Multiple Collection Creation and Batch Insertion in Typesense
Johan has a problem with creating multiple collections and batch-inserting documents into Typesense, which is returning results from different collections. Kishore Nallan helps troubleshoot the issue and suggests a potential local race condition, which is fixed in a later build.
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.
Cold Start Problem with Dynamic Collections
Adrian reported cold start issues with dynamic collections. Jason suggested using wildcard `*` for query_by parameters, upgrading to `0.25.0.rc34`, and clarified conventions. Adrian's issues were resolved but they reported a limitation that will potentially be addressed.
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.
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.