From 3227149e64deed46309ca858abb1af7f69c22485 Mon Sep 17 00:00:00 2001 From: Liam Thompson Date: Thu, 24 Apr 2025 13:55:54 +0200 Subject: [PATCH] [DOCS][8.x] Clarify update behavior for indices with semantic_text fields, flag CCS/CCR limitation --- docs/reference/mapping/types/semantic-text.asciidoc | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/reference/mapping/types/semantic-text.asciidoc b/docs/reference/mapping/types/semantic-text.asciidoc index bbff865446c7f..9a5e08075d5a4 100644 --- a/docs/reference/mapping/types/semantic-text.asciidoc +++ b/docs/reference/mapping/types/semantic-text.asciidoc @@ -222,8 +222,10 @@ In these cases - when you use `sparse_vector` or `dense_vector` field types inst [[update-script]] ==== Updates to `semantic_text` fields -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 https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-update[Update API]. +* Are not supported through the https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-bulk-1[Bulk API] and will fail. Even if the script targets non-`semantic_text` fields, the update will fail when the index contains a `semantic_text` field. [discrete] [[copy-to-support]] @@ -285,3 +287,4 @@ PUT test-index * `semantic_text` fields are not currently supported as elements of <>. * `semantic_text` fields can't currently be set as part of <>. +* `semantic_text` fields are currently not supported with Cross-Cluster Search (CCS) or Cross-Cluster Replication (CCR).