The application may be able to obtain a CRC32C checksum in some out-of-band way. For example, if the object was downloaded from some other cloud storage service, or because the application already queried the GCS object metadata. In these cases, providing the value to the client library improves the end-to-end data integrity verification.
[[["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-04-01 UTC."],[[["This webpage provides access to documentation for various versions of the `Crc32cChecksumValue` in Google Cloud Storage, ranging from the latest release candidate `2.37.0-rc` down to version `2.11.0`."],["The `Crc32cChecksumValue` allows users to pre-compute a CRC32C checksum to enhance data integrity verification, especially when the object's checksum is known beforehand, for instance from another cloud service or by previously querying the GCS object metadata."],["The Crc32cChecksumValue provides a static function named `name()` which returns the type `char const *`."],["The content includes a reference to a paper that further discusses this, found at this link: \u003chttps://sigops.org/s/conferences/hotos/2021/papers/hotos21-s01-hochschild.pdf\u003e."]]],[]]
