You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/elasticsearch/mapping-reference/semantic-text.md
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,10 @@ to `bbq_hnsw` automatically.
39
39
40
40
## Default and custom endpoints
41
41
42
+
You can use either preconfigured endpoints in your `semantic_text` fields which
43
+
are ideal for most use cases or create custom endpoints and reference them in
44
+
the field mappings.
45
+
42
46
### Using the default ELSER endpoint
43
47
44
48
If you use the preconfigured `.elser-2-elasticsearch` endpoint, you can set up
@@ -109,7 +113,7 @@ stack: preview 9.1
109
113
serverless: preview
110
114
```
111
115
112
-
If you use the preconfigured `.elser-2-elastic` endpoint that utilizes the ELSER model as a service ([ELSER on EIS](docs-content://explore-analyze/elastic-inference/eis.md#elser-on-eis)), you can
116
+
If you use the preconfigured `.elser-2-elastic` endpoint that utilizes the ELSER model as a service through the Elastic Inference Service ([ELSER on EIS](docs-content://explore-analyze/elastic-inference/eis.md#elser-on-eis)), you can
113
117
set up `semantic_text` with the following API request:
114
118
115
119
```console
@@ -126,8 +130,11 @@ PUT my-index-000001
126
130
}
127
131
```
128
132
133
+
::::{note}
129
134
While we do encourage experimentation, we do not recommend implementing production use cases on top of this feature while it is in Technical Preview.
130
135
136
+
::::
137
+
131
138
## Parameters for `semantic_text` fields [semantic-text-params]
0 commit comments