[DOCS] Clarify update behavior for indices with semantic_text fields, flag CCS/CCR limitation (#127310)

This commit is contained in:
Liam Thompson 2025-04-24 12:19:48 +02:00 committed by GitHub
parent 792b2428bf
commit 7b95ec4767
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 4 deletions

View File

@ -247,9 +247,10 @@ is not supported for querying the field data.
## Updates to `semantic_text` fields [update-script]
Updates that use scripts are not supported for an index contains a
`semantic_text` field. Even if the script targets non-`semantic_text` fields,
the update will fail when the index contains a `semantic_text` field.
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]
@ -311,4 +312,4 @@ PUT test-index
of [nested fields](/reference/elasticsearch/mapping-reference/nested.md).
* `semantic_text` fields cant currently be set as part
of [Dynamic templates](docs-content://manage-data/data-store/mapping/dynamic-templates.md).
* `semantic_text` fields are not supported with Cross-Cluster Search (CCS) or Cross-Cluster Replication (CCR).