feat(storage): capture metadata info in downloads#7694
feat(storage): capture metadata info in downloads#7694coryan merged 1 commit intogoogleapis:mainfrom
Conversation
|
Google Cloud Build Logs
ℹ️ NOTE: Kokoro logs are linked from "Details" below. |
|
Google Cloud Build Logs
ℹ️ NOTE: Kokoro logs are linked from "Details" below. |
402cd0c to
17bae99
Compare
|
Google Cloud Build Logs
ℹ️ NOTE: Kokoro logs are linked from "Details" below. |
17bae99 to
34dec08
Compare
|
Google Cloud Build Logs
ℹ️ NOTE: Kokoro logs are linked from "Details" below. |
34dec08 to
e4a1f93
Compare
|
Google Cloud Build Logs
ℹ️ NOTE: Kokoro logs are linked from "Details" below. |
e4a1f93 to
a51f215
Compare
|
Google Cloud Build Logs
ℹ️ NOTE: Kokoro logs are linked from "Details" below. |
a51f215 to
0e01d08
Compare
|
Google Cloud Build Logs
ℹ️ NOTE: Kokoro logs are linked from "Details" below. |
|
Google Cloud Build Logs
ℹ️ NOTE: Kokoro logs are linked from "Details" below. |
|
Google Cloud Build Logs
ℹ️ NOTE: Kokoro logs are linked from "Details" below. |
Codecov Report
@@ Coverage Diff @@
## main #7694 +/- ##
=======================================
Coverage 95.29% 95.30%
=======================================
Files 1256 1256
Lines 113697 113785 +88
=======================================
+ Hits 108350 108442 +92
+ Misses 5347 5343 -4
Continue to review full report at Codecov.
|
A lot of useful metadata information is included the the metadata headers for a GCS download over REST, and as an initial `Object` proto for gRPC. This information is needed to perform consistent reads from versioned objects (or detect inconsistent reads from objects without versioning). I will need this information as part of the changes for Arrow too.
c08521d to
3e5ea1e
Compare
|
Google Cloud Build Logs
ℹ️ NOTE: Kokoro logs are linked from "Details" below. |
|
After too many iterations this is now ready. PTaL. |
|
|
||
| auto is = client->ReadObject(bucket_name(), object_name, | ||
| Generation(insert->generation())); | ||
| EXPECT_EQ(insert->generation(), is.generation().value_or(0)); |
There was a problem hiding this comment.
why are the .value_or()s necessary?
A lot of useful metadata information is included the the metadata
headers for a GCS download over REST, and as an initial
Objectprotofor gRPC. This information is needed to perform consistent reads from
versioned objects (or detect inconsistent reads from objects without
versioning). I will need this information as part of the changes for
Arrow too.
Fixes #7677
This change is