From 78c91adeedb9d81ac8ce5b4db26e2c299ffce6ff Mon Sep 17 00:00:00 2001 From: David Turner Date: Fri, 28 Nov 2025 07:29:38 +0000 Subject: [PATCH] Update `unsafely_incompatible_with_s3_conditional_writes` version This change was backported to 9.2.3 in elastic/elasticsearch#138735, updating the `applies_to` marker to match. --- deploy-manage/tools/snapshot-and-restore/s3-repository.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/tools/snapshot-and-restore/s3-repository.md b/deploy-manage/tools/snapshot-and-restore/s3-repository.md index a7d5edd3b2..c53945cb84 100644 --- a/deploy-manage/tools/snapshot-and-restore/s3-repository.md +++ b/deploy-manage/tools/snapshot-and-restore/s3-repository.md @@ -233,7 +233,7 @@ The following settings are supported: `get_register_retry_delay` : ([time value](elasticsearch://reference/elasticsearch/rest-apis/api-conventions.md#time-units)) Sets the time to wait before trying again if an attempt to read a [linearizable register](#repository-s3-linearizable-registers) fails. Defaults to `5s`. -`unsafely_incompatible_with_s3_conditional_writes` {applies_to}`stack: ga 9.3` +`unsafely_incompatible_with_s3_conditional_writes` {applies_to}`stack: ga 9.2.3` : (boolean) {{es}} uses AWS S3's support for conditional writes to protect against repository corruption. If your repository is based on a storage system which claims to be S3-compatible but does not accept conditional writes, set this setting to `true` to make {{es}} perform unconditional writes, bypassing the repository corruption protection, while you work with your storage supplier to address this incompatibility with AWS S3. Defaults to `false`. ::::{note}