Avishay Guttman

When should I open the new stream(s)? Create x streams in advance to handle the chunks or only in case this error return create new stream and retry send the...

Thanks, I've refactor the code to use managedwriter, I will check it's behavior on high traffic ``` func do() error { // .... chunkSize := 10000 chunks := make([]interface{}, 0,...

Using the code above with high throughput also generated error "stream.GetResult(): rpc error: code = Unavailable desc = the connection is draining" and another quota error: "stream.AppendRows(): rpc error: code...

Thanks for help! I see now that I need to watch out to not write too fast because of the MB/s quota.. I'm still learning how this api works, we...

Another implementation with retry logic, in case of specific errors I'm trying again with a new stream connection. One thing I'm not sure is how to handle throughput error (ResourceExhausted),...

Hi @shollyman There are another errors we encounter every now and then: - `stream.GetResult(): rpc error: code = Internal desc = Internal error encountered. Entity: projects/project-id/datasets/dataset-id/tables/table-id/streams/_default` - `stream.GetResult(): rpc error:...

How did you fix it? I don't think downgrade svelte to run tests is a proper solution, also it makes another issues in the app itself

also regarding the documentation and what @DRK3 wrote: ``` // Client returns an HTTP client wrapping the context's // HTTP transport and adding Authorization headers with tokens // obtained from...

@DRK3 in the meantime I use this workaround ``` httpClient := &http.Client{ Transport: jwtCfg.Client(ctx).Transport, Timeout: 30 * time.Second, } ```