New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
storage: determine what to do on chunksize=0 [GRPC] #7798
Labels
api: storage
Issues related to the Cloud Storage API.
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: process
A process-related concern. May include testing, release, or the like.
Comments
product-auto-label
bot
added
the
api: storage
Issues related to the Cloud Storage API.
label
Apr 20, 2023
BrennaEpp
added
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: process
A process-related concern. May include testing, release, or the like.
and removed
api: storage
Issues related to the Cloud Storage API.
triage me
I really want to be triaged.
labels
Apr 20, 2023
product-auto-label
bot
added
the
api: storage
Issues related to the Cloud Storage API.
label
Apr 20, 2023
tritone
added a commit
to tritone/google-cloud-go
that referenced
this issue
May 2, 2023
tritone
added a commit
to tritone/google-cloud-go
that referenced
this issue
Jul 28, 2023
When ChunkSize is zero, use a single shot upload (leaving the stream open between messages) rather than a resumable session. This matches better with what we do in JSON. Also reduce the buffer size to the minimum (256k). Fixes googleapis#7798
gcf-merge-on-green bot
pushed a commit
that referenced
this issue
Aug 1, 2023
When ChunkSize is zero, use a single shot upload (leaving the stream open between messages) rather than a resumable session. This matches better with what we do in JSON. Also reduce the buffer size to the minimum (256k). Fixes #7798
Changed the chunkSize=0 logic to do the following:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
api: storage
Issues related to the Cloud Storage API.
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: process
A process-related concern. May include testing, release, or the like.
Address TODOs around L1472 in grpc_client.go
Should we actually use the minimum of 256 KB here [chunksize=0] when the user indicates they want minimal memory usage? We cannot do a zero-copy, bufferless upload like HTTP/JSON can.
Must make a note to update documentation accordingly.
The text was updated successfully, but these errors were encountered: