Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

GCSDataStore metadata get/set

See original GitHub issue

It appears you can’t save metadata to an GCS object until the upload is complete. We need to figure out how to set/get upload_length, upload_defer_length from a GCS upload_id for POST/HEAD requests.

Issue Analytics

State:
Created 7 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

bhstahlcommented, May 23, 2016

Ahh i see what you were saying @js3692. We can store metadata on the objects, and I actually just got it working, so no need for an extra file to store json 😄

0reactions

js3692commented, May 22, 2016

Thanks for explaining that! My point also was to persist everything on GCS (sorry if that wasn’t clear) - when the POST request comes in with the metadata, the server will persist the data to GCS (see image below) with the above file.save. This is an extra http cycle between the server and GCS, but I was wondering if it could be an alternative to the issue highlighted above.

Top Results From Across the Web

Object metadata | Cloud Storage - Google Cloud

Objects stored in Cloud Storage have metadata associated with them. Metadata identifies properties of the object, as well as specifies how the object...