Bug Report: Error after Editing Built-In Embedding Field
TLDR Gustavo reported a bug with an error after editing a built-in embedding field in the schema. Jason acknowledged the report.
1Jun 09, 2023 (3 months ago)
Gustavo
07:18 PMfrom fields, upserting starts throwing an error: Field 'embedding' has been declared in the schema, but is not found in the document. If I delete the collection and recreate with the exact same schema, I can upsert documents again.
Jason
07:23 PM1
Typesense
Indexed 2764 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.
1Issues 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.
8Resolving Issue with Auto Embedding Generation from Two Fields
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