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 page 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 like `None`, `ThrowOnly`, and `DeleteAndThrow`."],["`DeleteAndThrow` computes the hash of the uploaded data, attempts to delete the object if the hash differs, and throws an `UploadValidationException` in either case."],["`ThrowOnly` also computes the data hash and throws an `UploadValidationException` if there's a discrepancy, but does not delete the object."],["The page lists the various versions of the Google Cloud Storage v1 API, from version 3.4.0 to the latest 4.11.0, that include the UploadValidationMode documentation."]]],[]]