diff --git a/docs/reference/elasticsearch/mapping-reference/semantic-text.md b/docs/reference/elasticsearch/mapping-reference/semantic-text.md index b639534626b88..7ae0311031c70 100644 --- a/docs/reference/elasticsearch/mapping-reference/semantic-text.md +++ b/docs/reference/elasticsearch/mapping-reference/semantic-text.md @@ -437,8 +437,16 @@ When updating documents that contain `semantic_text` fields, it’s important to If you want to avoid unnecessary inference and keep existing embeddings: - * Use **partial updates through the Bulk API**. - * Omit any `semantic_text` fields that did not change from the `doc` object in your request. + * Use **partial updates through the Bulk API**. + * Omit any `semantic_text` fields that did not change from the `doc` object in your request. + +### Scripted updates + +For indices containing `semantic_text` fields, updates that use scripts have the +following behavior: + +- ✅ **Supported:** [Update API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-update) +- ❌ **Not supported:** [Bulk API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-bulk-1). Scripted updates will fail even if the script targets non-`semantic_text` fields. ## Returning semantic field embeddings in `_source` @@ -578,18 +586,6 @@ PUT my-index-000004 ``` % TEST[skip:Requires inference endpoint] -## Updates to `semantic_text` fields [update-script] - -For indices containing `semantic_text` fields, updates that use scripts have the -following behavior: - -* Are supported through - the [Update API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-update). -* Are not supported through - the [Bulk API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-bulk-1) - and will fail. Even if the script targets non-`semantic_text` fields, the - update will fail when the index contains a `semantic_text` field. - ## `copy_to` and multi-fields support [copy-to-support] The semantic_text field type can serve as the target