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-09 UTC."],[[["This webpage provides access to the `Crc32cChecksumValue` documentation for various versions, including the latest release candidate, 2.37.0-rc, and historical versions down to 2.11.0."],["The `Crc32cChecksumValue` function allows for the input of pre-computed CRC32C checksums, enhancing data integrity verification if the checksum is already known."],["The document features a static `name()` function, the details of which can be found within the individual version entries of `Crc32cChecksumValue`."],["The documentation provides a reference to a relevant research paper on the topic of cloud storage and data integrity, located here: \u003chttps://sigops.org/s/conferences/hotos/2021/papers/hotos21-s01-hochschild.pdf\u003e."]]],[]]
