Skip to content

Commit f83882a

Browse files
committed
Addresses feedback.
1 parent 093dc57 commit f83882a

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

docs/reference/elasticsearch/mapping-reference/semantic-text.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,10 @@ to `bbq_hnsw` automatically.
3939

4040
## Default and custom endpoints
4141

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+
4246
### Using the default ELSER endpoint
4347

4448
If you use the preconfigured `.elser-2-elasticsearch` endpoint, you can set up
@@ -109,7 +113,7 @@ stack: preview 9.1
109113
serverless: preview
110114
```
111115

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
113117
set up `semantic_text` with the following API request:
114118

115119
```console
@@ -126,8 +130,11 @@ PUT my-index-000001
126130
}
127131
```
128132

133+
::::{note}
129134
While we do encourage experimentation, we do not recommend implementing production use cases on top of this feature while it is in Technical Preview.
130135

136+
::::
137+
131138
## Parameters for `semantic_text` fields [semantic-text-params]
132139

133140
`inference_id`

0 commit comments

Comments
 (0)