Resolving Issue with Auto Embedding Generation from Two Fields
TLDR Ayush asked about a problem with autoembedding when one of the fields could be empty. Kishore Nallan suggested that the issue might be a bug related to upsert and recommended him to check the 0.24.1.rc6 build.
1
Sep 01, 2023 (3 months ago)
Ayush
09:25 AMKishore Nallan
09:29 AMAyush
09:38 AMKishore Nallan
09:44 AM1
Typesense
Indexed 3011 threads (79% resolved)
Similar Threads
Troubleshooting Typesense Node Embedding Field Error after Upgrade
Denny was having an error with the embedding field after upgrading a typesense node. Jason revealed that this was a bug in the v0.25.0 version. They suggested upgrading to 0.25.1.rc4 to fix the issue, which Denny did successfully.
Issues with Cluster Upgrade and Embedding Field
Gustavo had issues upgrading their cluster and their embedding field wasn't being filled. Jason helped to solve the upgrade issue and advised re-indexing the documents to solve the embedding field issue. Both problems were successfully resolved.
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.