|author||Jean de Klerk <firstname.lastname@example.org>||Fri Jun 07 17:02:15 2019 -0600|
|committer||Jean de Klerk <email@example.com>||Thu Oct 10 10:03:16 2019 -0600|
pubsub: add ordered keys Pub/Sub ordered keys requires: - Publish with a non-empty key gets added to a per-key queue, as implemented by Bundler.HandlerLimit=1. This setting causes the bundler to only have one outstanding bundle being handled at a time; further bundles form a queue. - Receive with a message that has a non-empty key gets added to a per-key queue, as implemented by a slice. When a worker operates on a key, it processes all items in the key's slice until the slice is empty, at which point it deletes the key to release the key's resources, and the worker returns to the worker pool. Functionally, for users, this should involve: - Slightly slower processing speeds due to additional data structures along the Publish and Receive paths. (we should do some performance testing to vet this out) - PublishSettings.NumGoroutines and ReceiveSettings.NumGoroutines should both result in double the number of goroutines, since an additional data structure (publish/receive scheduler) uses that value. Documentation has been adjusted accordingly to describe it more as a scaling factor than an exact number. - Default ReceiveSettings.NumGoroutines is increased from 1 to 10. It's generally a better experience to have multiple workers than one. And, some tests - like TestStreamingPullFlowControl - implicitly require it. - Since ordered keys require only a single outstanding RPC at once, it is possible to send ordered key messages to Topic.Publish (and subsequently to PublishScheduler.Add) faster than the bundler can publish them to the Pub/Sub service, resulting in a backed up queue of Pub/Sub bundles. Each item in the bundler queue is a goroutine, which means users may see thousands of goroutines in debugging they might do. TODO: add Resume method. Change-Id: Ib710944d557970290cf12321d1fdbd9b1699231d
Go packages for Google Cloud Platform services.
To install the packages on your system, do not clone the repo. Instead use
$ go get -u cloud.google.com/go/...
NOTE: Some of these packages are under development, and may occasionally make backwards-incompatible changes.
NOTE: Github repo is a mirror of https://code.googlesource.com/gocloud.
|Data Loss Prevention||alpha|
|Text To Speech||alpha|
Alpha status: the API is still being actively developed. As a result, it might change in backward-incompatible ways and is not recommended for production use.
Beta status: the API is largely complete, but still has outstanding features and bugs to be addressed. There may be minor backwards-incompatible changes where necessary.
Stable status: the API is mature and ready for production use. We will continue addressing bugs and feature requests.
Documentation and examples are available at godoc.org/cloud.google.com/go
We support the two most recent major versions of Go. If Google App Engine uses an older version, we support that as well.
By default, each API will use Google Application Default Credentials for authorization credentials used in calling the API endpoints. This will allow your application to run in many environments without requiring explicit configuration.
client, err := storage.NewClient(ctx)
To authorize using a JSON key file, pass
option.WithCredentialsFile to the
NewClient function of the desired package. For example:
client, err := storage.NewClient(ctx, option.WithCredentialsFile("path/to/keyfile.json"))
You can exert more control over authorization by using the
golang.org/x/oauth2 package to create an
oauth2.TokenSource. Then pass
option.WithTokenSource to the
NewClient function: snip:# (auth-ts)
tokenSource := ... client, err := storage.NewClient(ctx, option.WithTokenSource(tokenSource))
Contributions are welcome. Please, see the CONTRIBUTING document for details. We‘re using Gerrit for our code reviews. Please don’t open pull requests against this repo, new pull requests will be automatically closed.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms. See Contributor Code of Conduct for more information.