#community-help

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.

3mo

Join the chat

Sep 01, 2023 (3 months ago)

Photo of md5-b599fe398728a1867404c6c8ef6e98de

Ayush

09:25 AM

Hei we're using generating auto embedding from two fields but one of the field can be an empty string . Which leads to autoembedding being not created , Is there an way to circumvent this issue , i.e having a default value or not using the other field to create embeddings when it's empty ?

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

09:29 AM

Hi Ayush, what error are you getting when one of the fields are empty?

Ayush

09:38 AM

No error logs there , so far . Just an empty embedding field

Kishore Nallan

09:44 AM

This might be a bug related to upsert and not because of empty value. Check the 0.24.1.rc6 build which contains a fix.

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3011 threads (79% resolved)

Join Our Community

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.

3mo

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.

3mo

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.

24mo