The hash of the data is computed while uploading, and
if the resulting object has a different hash, an attempt is made to delete the object.
Whether the deletion fails or not, an UploadValidationException
is thrown. If the deletion fails, that failure can be examined via
AdditionalFailures
None
The upload is not validated.
ThrowOnly
The hash of the data is computed while uploading, and
if the resulting object has a different hash, an UploadValidationException
is thrown, but the object remains present in Storage.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["This webpage details the `UploadValidationMode` enum within the `Google.Cloud.Storage.V1` namespace, found in the Google.Cloud.Storage.V1.dll assembly."],["The `UploadValidationMode` enum defines three distinct behaviors for data upload validation: `None`, `ThrowOnly`, and `DeleteAndThrow`."],["The latest version for the Google.Cloud.Storage.V1 component is 4.11.0 and the page details all versions down to 3.4.0."],["When `DeleteAndThrow` is used, data integrity is checked during the upload and if a mismatch is found, an attempt to delete the uploaded object will occur followed by throwing an `UploadValidationException`."],["`ThrowOnly` mode also validates data during upload, throwing an `UploadValidationException` upon a hash mismatch, but the object will remain in Storage, and the `None` option bypasses all validation."]]],[]]