#community-help

Issue with Embedding Error in Version 0.25.0.rc63

TLDR Bill reported a bug in version 0.25.0.rc63 regarding a problem with updating or emplacing a document and receiving an embedding error. This was resolved in version 0.25.0.rc65, but further discussion ensued regarding the function of 'index' in the update feature.

1mo

Join the chat

Aug 10, 2023 (1 month ago)

Photo of md5-c3b34a63c854c8bedbeff235c64dcaa5

Bill

12:45 PM

Hello, I've found a bug in version 0.25.0.rc63. When I try to Update or Emplace a document I receive this error:
POST ../documents?action=emplace -> "message": "No valid fields found to create embedding for embedding, please provide at least one valid field or make the embedding field optional." with payload:
{
"id": "602",
"about": "test"
}

this also happens with action=update

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

12:47 PM

Hi Bill. Is the field already optional in the schema?

Bill

12:47 PM

No the embedding field is not optional

Kishore Nallan

12:48 PM

I actually fixed a bug which was not enforcing this.

Bill

12:48 PM

I didn't have this issue with previous versions

Kishore Nallan

12:48 PM

This is for auto embedding?

Bill

12:48 PM

Yes

Kishore Nallan

12:49 PM

Ok maybe that was not considered. I'll look shortly. Would you be able to post a small snippet that reproduces the issue?

Bill

12:50 PM

12:55

Bill

12:55 PM

In order to reproduce it,
Create the collection

curl "<http://localhost:8108/collections>" \
-X POST \
-H "Content-Type: application/json" \
-H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" \
-d '
{
"name": "products",
"fields": [
{
"name": "product_name",
"type": "string"
},
{
"name": "about",
"type": "string"
},
{
"name": "embedding",
"type": "float[]",
"embed": {
"from": [
"product_name",
"about"
],
"model_config": {
"model_name": "ts/paraphrase-multilingual-mpnet-base-v2"
}
}
}
]
}
'

12:56

Bill

12:56 PM

Index a doc

curl "<http://localhost:8108/collections/products/documents/import?action=create>" \
-H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" \
-H "Content-Type: text/plain" \
-X POST \
-d '
{"product_name": "ABCD","about": "This is some description text"}
'

12:58

Bill

12:58 PM

Update the doc

curl "<http://localhost:8108/collections/products/documents?action=emplace>" \
-H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" \
-H "Content-Type: text/plain" \
-X POST \
-d '
{"id": "1","about": "Test"}
'

Kishore Nallan

12:59 PM

Thanks, will fix shortly. Regression introduced in rc63 or rc62

Bill

01:00 PM

Kishore Nallan

01:32 PM

Wait, the update doesn't have the field product_name

Bill

01:33 PM

I want to update only the about field, I use emplace for this reason

Kishore Nallan

01:34 PM

Ok got it.

01:35

Kishore Nallan

01:35 PM

> this also happens with action=update
But it works with action=update for me.

01:35

Kishore Nallan

01:35 PM

And your earlier error message at the start of the thread is different

01:35

Kishore Nallan

01:35 PM

No valid fields found to create embedding for `embedding`, please provide at least one valid field or make the embedding field optional.

01:35

Kishore Nallan

01:35 PM

Is that a different issue?

Bill

01:36 PM

I use emplace to update part of the doc such as the about filed. I tried with update in order to check it, but I got the same error message:

No valid fields found to create embedding for `embedding`, please provide at least one valid field or make the embedding field optional.

01:37

Bill

01:37 PM

The main method I use to update docs is Emplace

Kishore Nallan

01:37 PM

Ok. Let me investigate further.

Bill

01:38 PM

01:39

Bill

01:39 PM

In order to reproduce it, just use emplace with only "id" and "about" fields

Kishore Nallan

01:40 PM

What message do you get when you run the above curl but with action=update instead of emplace?

Bill

01:41 PM

If i use update with this payload (without product_name) I get this error:
{
"message": "No valid fields found to create embedding for embedding, please provide at least one valid field or make the embedding field optional."
}

01:42

Bill

01:42 PM

I don't use Update method because it requires the full doc. I use only Emplace and update specific fields.

Kishore Nallan

02:07 PM

Bill There is an issue with the example above. For emplace "id": "1", is sent as the record ID. But the first record that gets indexed via action=create will actually get id: 0

Bill

02:09 PM

Yes my mistake id: 0

Kishore Nallan

02:09 PM

With that change, it works for me :thinking_face:

02:09

Kishore Nallan

02:09 PM

See this gist: https://gist.github.com/kishorenc/99b684ce9126db24b0775e1ef39b62e5

02:11

Kishore Nallan

02:11 PM

Can you try the above?

Bill

02:11 PM

Ok i'll try it

02:14

Bill

02:14 PM

I get the same error:
{
"message": "No valid fields found to create embedding for embedding, please provide at least one valid field or make the embedding field optional."
}

02:15

Bill

02:15 PM

I think i found the bug

02:16

Bill

02:16 PM

If you create the collection with this payload:
{
"name": "products",
"fields": [
{
"name": "product_name",
"type": "string"
},
{
"name": "about",
"type": "string"
},
{
"name": "embedding",
"type": "float[]",
"embed": {
"from": [
"product_name"
],
"model_config": {
"model_name": "ts/paraphrase-multilingual-mpnet-base-v2"
}
}
}
]
}

02:16

Bill

02:16 PM

Index a doc

Kishore Nallan

02:16 PM

Hmm then how is it working for me :thinking_face: are you using the deb? Maybe I'm not reproducing it properly.

Bill

02:16 PM

and use emplace

Kishore Nallan

02:16 PM

Model name matters?

Bill

02:16 PM

I use rc63