From da8a2588e3674b388b773e2491db7c8af737e055 Mon Sep 17 00:00:00 2001 From: as598466 <124391092+as598466@users.noreply.github.com> Date: Fri, 5 Dec 2025 09:08:32 +0100 Subject: [PATCH] Document default setting for validateWrites Added note about 'validateWrites' default setting for object stores. Signed-off-by: as598466 <124391092+as598466@users.noreply.github.com> --- admin_manual/configuration_files/primary_storage.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/admin_manual/configuration_files/primary_storage.rst b/admin_manual/configuration_files/primary_storage.rst index 71af98152d9..b4e35082d19 100644 --- a/admin_manual/configuration_files/primary_storage.rst +++ b/admin_manual/configuration_files/primary_storage.rst @@ -203,6 +203,7 @@ Optional parameters less commonly needing adjustment: * :code:`legacy_auth` has no default * :code:`version` defaults to :code:`latest` * :code:`verify_bucket_exists` defaults to :code:`true` [Note: Setting this to :code:`false` *after* confirming the bucket has been created may provide a performance benefit, but may not be possible in multibucket scenarios.] +* :code:`validateWrites` defaults to :code:`true` [Note: Setting this to :code:false is recommended for object stores with "eventual consistency". It prevents false errors where a file is successfully uploaded but not yet visible to an immediate check.] **If you are using Amazon S3:** the :code:`region` parameter is required unless you're happy with the default of :code:`eu-west-1`. There is no need to override the :code:`hostname` or :code:`port`.