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 document provides reference documentation for the `UploadValidationMode` enum within the Google Cloud Storage v1 API."],["The `UploadValidationMode` enum defines how data upload validation should behave, with options to either do nothing, throw an exception, or delete and throw an exception upon mismatch."],["The latest version documented for this enum is 4.11.0, while version 4.3.0 is the specific version for which detailed descriptions are given."],["There are three defined fields in the `UploadValidationMode` enum: `DeleteAndThrow`, `None`, and `ThrowOnly`, each with specific behaviors regarding the validation of uploaded data."],["This documentation covers versions 3.4.0 through 4.11.0 of this enum."]]],[]]