Skip to content

Commit 840a7b8

Browse files
💅
1 parent b7b0fa0 commit 840a7b8

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

‎.code-samples.meilisearch.yaml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1548,4 +1548,4 @@ search_parameter_reference_media_1: |-
15481548
"FIELD_D": "VALUE_C"
15491549
}
15501550
}
1551-
}'
1551+
}'

‎reference/api/settings.mdx‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2513,8 +2513,8 @@ These embedder objects may contain the following fields:
25132513
| **`indexingEmbedder`** | Object | Empty | Configures embedder to vectorize documents during indexing |
25142514
| **`searchEmbedder`** | Object | Empty | Configures embedder to vectorize search queries |
25152515
| **`pooling`** | String | `"useModel"` | Pooling method for Hugging Face embedders |
2516-
| **`indexingFragments`** | Object | Empty | Configures a set of fields for multimodal embedding generation |
2517-
| **`searchFragments`** | Object | Empty | Configures a set of fields for use in multimodal search |
2516+
| **`indexingFragments`** | Object | Empty | Configures multimodal embedding generation at indexing time |
2517+
| **`searchFragments`** | Object | Empty | Configures data handling during multimodal search |
25182518

25192519
### Get embedder settings
25202520

@@ -2892,7 +2892,7 @@ curl \
28922892
```
28932893
</Note>
28942894

2895-
`indexingFragments` specifies which fields in your documents should be used during multimodal embedding generation. It must be an object with the following structure:
2895+
`indexingFragments` specifies which fields in your documents should be used to generate multimodal embeddings. It must be an object with the following structure:
28962896

28972897
```json
28982898
"FRAGMENT_NAME": {
@@ -2908,7 +2908,7 @@ For example, for Voyage AI's text and image embedder, `value` must be an array c
29082908

29092909
```json
29102910
{
2911-
"FRAGMENT_NAME_A": {
2911+
"VOYAGE_FRAGMENT_NAME_A": {
29122912
"value": {
29132913
"content": [
29142914
{
@@ -2918,7 +2918,7 @@ For example, for Voyage AI's text and image embedder, `value` must be an array c
29182918
]
29192919
}
29202920
},
2921-
"FRAGMENT_NAME_B": {
2921+
"VOYAGE_FRAGMENT_NAME_B": {
29222922
"value": {
29232923
"content": [
29242924
{
@@ -2968,7 +2968,7 @@ curl \
29682968

29692969
As with `indexingFragments`, the content of `value` should follow your model's specification.
29702970

2971-
Use Liquid templates to interpolate search query data into the fragment fields, where `media` gives you access to all that parameter's fields:
2971+
Use Liquid templates to interpolate search query data into the fragment fields, where `media` gives you access to all multimodal data received with a query:
29722972

29732973
```json
29742974
"SEARCH_FRAGMENT_A": {

0 commit comments

Comments
 (0)